Reliable control signaling

ABSTRACT

Systems, methods, and instrumentalities are disclosed for reliable control signaling, for example, in New Radio (NR). A receiver in a wireless transmit/receive unit (WTRU) may receive one or more physical downlink control channel (PDCCH) transmissions comprising downlink control information (DCI). The WTRU may determine a transmission profile associated with an uplink control information (UCI). Based on the transmission profile, the WTRU may determine one or more transmission characteristics associated with the transmission of the UCI. The WTRU may transmit the UCI over a physical uplink control channel (PUCCH). The UCI may be transmitted using transmission characteristics determined by the WTRU. The WTRU may transmit the UCI based on at least one of a control resource set (CORESET), a search space, or a radio network temporary identifier (RNTI). The WTRU may determine a transmission profile differently based on what the UCI may comprise.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication Nos. 62/519,585 filed on Jun. 14, 2017, 62/585,937 filed onNov. 14, 2017, 62/652,002 filed on Apr. 3, 2018, and 62/667,015 filed onMay 4, 2018, the contents of which are hereby incorporated by referenceherein.

BACKGROUND

Mobile communications using wireless communication continue to evolve. Afifth generation or Next Gen (NG) wireless systems may be referred to as5G or New Radio (NR). A previous generation of mobile communication maybe, for example, fourth generation (4G) long term evolution (LTE). A setof use cases for NR may be generally classified into one of an enhancedmobile broadband (eMBB), an ultra-reliable and low-latencycommunications (URLLC), or massive machine type communication (mMTC).Current processing and transmission mechanisms used for such uses casesmay be less efficient.

SUMMARY

Systems, methods, and instrumentalities are disclosed for reliablecontrol signaling, for example, in New Radio (NR). A receiver in awireless transmit/receive unit (WTRU) may receive one or more physicaldownlink control channel (PDCCH) transmissions comprising downlinkcontrol information (DCI). The WTRU may determine a transmission profileassociated with an uplink control information (UCI). The transmissionprofile may be determined based on one or more of the following: anidentity of a logical channel or a logical channel group for dataassociated with the UCI, and a property of the at least one PDCCHtransmission. The PDCCH transmission may be mapped to one or moreresources of a control resource set (CORESET).

The transmission profile may be determined based on one or more of: oneor more DCI fields in the received DCI, or an identity of a bandwidthpart (BWP) used for transmitting one or more of the DCI or the UCI.

The DCI may include a first DCI and a second DCI. A DCI field mayindicate a hybrid automatic repeat request (HARQ) process index or alogical channel priority. The first DCI may be received using a firstcontrol resource set (CORESET), and the second DCI may be received usinga second CORESET. The first CORESET or the second CORESET may includeone or more of the following: a component carrier, at least one BWP, asubset of resource blocks within each bandwidth part, a set of timesymbols within a slot or mini-slot, a sub-carrier spacing, a subset ofslots within a subframe, or at least one reference signal.

The UCI may include a first UCI and a second UCI. The first UCI or thesecond UCI may include one or more of a hybrid automatic repeat request(HARQ), a scheduling request (SR), or a channel quality indicator (CQI).The UCI may be transmitted based on a CORESET, a search space, or aRNTI. The UCI may be associated with a PDSCH transmission or a PDCCHtransmission. In an example, the first UCI or the second UCI may includefeedback information bits for a data transmission allocated by the firstDCI or the second DCI. In another example, the second UCI may correspondto a redundant transmission of the first UCI.

Based on the transmission profile, the WTRU may determine one or moretransmission characteristics associated with the transmission of theUCI. The one or more transmission characteristics may include at leastone of the following: one or more coding parameters, one or moretransmission power parameters, one or more resource allocationparameters, or a priority level.

The WTRU may transmit the UCI over a physical uplink control channel(PUCCH). The UCI may be transmitted using transmission characteristicsdetermined by the WTRU. The WTRU may transmit the UCI based on one ormore of a CORESET, a search space, or a radio network temporaryidentifier (RNTI). The PUCCH carrying the UCI may be transmitted on anuplink (UL) carrier and/or a supplementary uplink (SUL) carrier.

The WTRU may determine a transmission profile associated with a PDSCHtransmission based on one or more of the following, for example, if theUCI comprises a hybrid automatic repeat request acknowledgement (HARQACK): a duration of the transmission, a bandwidth part, a numerology, ora modulation and coding scheme (MCS) table for control information.

The WTRU may determine a transmission profile based on one or more ofthe following, for example, if the UCI comprises a channel stateinformation (CSI): a value of block error rate (BLER) target associatedwith the CSI, or a CSI report setting.

The WTRU may determine a transmission profile based on one or more ofthe following, for example, if the UCI comprises a scheduling request(SR) associated with a physical uplink control channel (PUCCH) resourceconfigured for a transmission of the SR: a sub-carrier spacing, aduration of a PUCCH resource, a logical channel associated with an SRconfiguration, a priority associated with the logical channel.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description,given by way of example in conjunction with the accompanying drawings.

FIG. 1A is a system diagram illustrating an example communicationssystem in which one or more disclosed embodiments may be implemented.

FIG. 1B is a system diagram illustrating an example wirelesstransmit/receive unit (WTRU) that may be used within the communicationssystem illustrated in FIG. 1A.

FIG. 1C is a system diagram illustrating an example radio access network(RAN) and an example core network (CN) that may be used within thecommunications system illustrated in FIG. 1A.

FIG. 1D is a system diagram illustrating a further example RAN and afurther example CN that may be used within the communications systemillustrated in FIG. 1A.

FIG. 2 illustrates an example of downlink control information (DCI)diversity.

FIG. 3 illustrates an example of DCI and uplink control information(UCI) diversity.

DETAILED DESCRIPTION

A detailed description of illustrative embodiments will now be describedwith reference to the various Figures. Although this descriptionprovides a detailed example of possible implementations, it should benoted that the details are intended to be exemplary and in no way limitthe scope of the application.

FIG. 1A is a diagram of an example communications system 100 in whichone or more disclosed embodiments may be implemented. The communicationssystem 100 may be a multiple access system that provides content, suchas voice, data, video, messaging, broadcast, etc., to multiple wirelessusers. The communications system 100 may enable multiple wireless usersto access such content through the sharing of system resources,including wireless bandwidth. For example, the communications systems100 may employ one or more channel access methods, such as code divisionmultiple access (CDMA), time division multiple access (TDMA), frequencydivision multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrierFDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-sOFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filterbank multicarrier (FBMC), and the like.

As shown in FIG. 1A, the communications system 100 may include wirelesstransmit/receive units (WTRUs) 102 a, 102 b, 102 c, 102 d, a RAN104/113, a CN 106/115, a public switched telephone network (PSTN) 108,the Internet 110, and other networks 112, though it will be appreciatedthat the disclosed embodiments contemplate any number of WTRUs, basestations, networks, and/or network elements. Each of the WTRUs 102 a,102 b, 102 c, 102 d may be any type of device configured to operateand/or communicate in a wireless environment. By way of example, theWTRUs 102 a, 102 b, 102 c, 102 d, any of which may be referred to as a“station” and/or a “STA”, may be configured to transmit and/or receivewireless signals and may include a user equipment (UE), a mobilestation, a fixed or mobile subscriber unit, a subscription-based unit, apager, a cellular telephone, a personal digital assistant (PDA), asmartphone, a laptop, a netbook, a personal computer, a wireless sensor,a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watchor other wearable, a head-mounted display (HMD), a vehicle, a drone, amedical device and applications (e.g., remote surgery), an industrialdevice and applications (e.g., a robot and/or other wireless devicesoperating in an industrial and/or an automated processing chaincontexts), a consumer electronics device, a device operating oncommercial and/or industrial wireless networks, and the like. Any of theWTRUs 102 a, 102 b, 102 c and 102 d may be interchangeably referred toas a UE.

The communications systems 100 may also include a base station 114 aand/or a base station 114 b. Each of the base stations 114 a, 114 b maybe any type of device configured to wirelessly interface with at leastone of the WTRUs 102 a, 102 b, 102 c, 102 d to facilitate access to oneor more communication networks, such as the CN 106/115, the Internet110, and/or the other networks 112. By way of example, the base stations114 a, 114 b may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller,an access point (AP), a wireless router, and the like. While the basestations 114 a, 114 b are each depicted as a single element, it will beappreciated that the base stations 114 a, 114 b may include any numberof interconnected base stations and/or network elements.

The base station 114 a may be part of the RAN 104/113, which may alsoinclude other base stations and/or network elements (not shown), such asa base station controller (BSC), a radio network controller (RNC), relaynodes, etc. The base station 114 a and/or the base station 114 b may beconfigured to transmit and/or receive wireless signals on one or morecarrier frequencies, which may be referred to as a cell (not shown).These frequencies may be in licensed spectrum, unlicensed spectrum, or acombination of licensed and unlicensed spectrum. A cell may providecoverage for a wireless service to a specific geographical area that maybe relatively fixed or that may change over time. The cell may furtherbe divided into cell sectors. For example, the cell associated with thebase station 114 a may be divided into three sectors. Thus, in oneembodiment, the base station 114 a may include three transceivers, i.e.,one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and mayutilize multiple transceivers for each sector of the cell. For example,beamforming may be used to transmit and/or receive signals in desiredspatial directions.

The base stations 114 a, 114 b may communicate with one or more of theWTRUs 102 a, 102 b, 102 c, 102 d over an air interface 116, which may beany suitable wireless communication link (e.g., radio frequency (RF),microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet(UV), visible light, etc.). The air interface 116 may be establishedusing any suitable radio access technology (RAT).

More specifically, as noted above, the communications system 100 may bea multiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. Forexample, the base station 114 a in the RAN 104/113 and the WTRUs 102 a,102 b, 102 c may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA), whichmay establish the air interface 115/116/117 using wideband CDMA (WCDMA).WCDMA may include communication protocols such as High-Speed PacketAccess (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-SpeedDownlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access(HSUPA).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement a radio technology such as Evolved UMTS TerrestrialRadio Access (E-UTRA), which may establish the air interface 116 usingLong Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/orLTE-Advanced Pro (LTE-A Pro).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement a radio technology such as NR Radio Access, which mayestablish the air interface 116 using New Radio (NR).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement multiple radio access technologies. For example, thebase station 114 a and the WTRUs 102 a, 102 b, 102 c may implement LTEradio access and NR radio access together, for instance using dualconnectivity (DC) principles. Thus, the air interface utilized by WTRUs102 a, 102 b, 102 c may be characterized by multiple types of radioaccess technologies and/or transmissions sent to/from multiple types ofbase stations (e.g., a eNB and a gNB).

In other embodiments, the base station 114 a and the WTRUs 102 a, 102 b,102 c may implement radio technologies such as IEEE 802.11 (i.e.,Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperabilityfor Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO,Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), InterimStandard 856 (IS-856), Global System for Mobile communications (GSM),Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and thelike.

The base station 114 b in FIG. 1A may be a wireless router, Home Node B,Home eNode B, or access point, for example, and may utilize any suitableRAT for facilitating wireless connectivity in a localized area, such asa place of business, a home, a vehicle, a campus, an industrialfacility, an air corridor (e.g., for use by drones), a roadway, and thelike. In one embodiment, the base station 114 b and the WTRUs 102 c, 102d may implement a radio technology such as IEEE 802.11 to establish awireless local area network (WLAN). In an embodiment, the base station114 b and the WTRUs 102 c, 102 d may implement a radio technology suchas IEEE 802.15 to establish a wireless personal area network (WPAN). Inyet another embodiment, the base station 114 b and the WTRUs 102 c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE,LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. Asshown in FIG. 1A, the base station 114 b may have a direct connection tothe Internet 110. Thus, the base station 114 b may not be required toaccess the Internet 110 via the CN 106/115.

The RAN 104/113 may be in communication with the CN 106/115, which maybe any type of network configured to provide voice, data, applications,and/or voice over internet protocol (VoIP) services to one or more ofthe WTRUs 102 a, 102 b, 102 c, 102 d. The data may have varying qualityof service (QoS) requirements, such as differing throughputrequirements, latency requirements, error tolerance requirements,reliability requirements, data throughput requirements, mobilityrequirements, and the like. The CN 106/115 may provide call control,billing services, mobile location-based services, pre-paid calling,Internet connectivity, video distribution, etc., and/or performhigh-level security functions, such as user authentication. Although notshown in FIG. 1A, it will be appreciated that the RAN 104/113 and/or theCN 106/115 may be in direct or indirect communication with other RANsthat employ the same RAT as the RAN 104/113 or a different RAT. Forexample, in addition to being connected to the RAN 104/113, which may beutilizing a NR radio technology, the CN 106/115 may also be incommunication with another RAN (not shown) employing a GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

The CN 106/115 may also serve as a gateway for the WTRUs 102 a, 102 b,102 c, 102 d to access the PSTN 108, the Internet 110, and/or the othernetworks 112. The PSTN 108 may include circuit-switched telephonenetworks that provide plain old telephone service (POTS). The Internet110 may include a global system of interconnected computer networks anddevices that use common communication protocols, such as thetransmission control protocol (TCP), user datagram protocol (UDP) and/orthe internet protocol (IP) in the TCP/IP internet protocol suite. Thenetworks 112 may include wired and/or wireless communications networksowned and/or operated by other service providers. For example, thenetworks 112 may include another CN connected to one or more RANs, whichmay employ the same RAT as the RAN 104/113 or a different RAT.

Some or all of the WTRUs 102 a, 102 b, 102 c, 102 d in thecommunications system 100 may include multi-mode capabilities (e.g., theWTRUs 102 a, 102 b, 102 c, 102 d may include multiple transceivers forcommunicating with different wireless networks over different wirelesslinks). For example, the WTRU 102 c shown in FIG. 1A may be configuredto communicate with the base station 114 a, which may employ acellular-based radio technology, and with the base station 114 b, whichmay employ an IEEE 802 radio technology.

FIG. 1B is a system diagram illustrating an example WTRU 102. As shownin FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120,a transmit/receive element 122, a speaker/microphone 124, a keypad 126,a display/touchpad 128, non-removable memory 130, removable memory 132,a power source 134, a global positioning system (GPS) chipset 136,and/or other peripherals 138, among others. It will be appreciated thatthe WTRU 102 may include any sub-combination of the foregoing elementswhile remaining consistent with an embodiment.

The processor 118 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. The processor 118 may perform signal coding, dataprocessing, power control, input/output processing, and/or any otherfunctionality that enables the WTRU 102 to operate in a wirelessenvironment. The processor 118 may be coupled to the transceiver 120,which may be coupled to the transmit/receive element 122. While FIG. 1Bdepicts the processor 118 and the transceiver 120 as separatecomponents, it will be appreciated that the processor 118 and thetransceiver 120 may be integrated together in an electronic package orchip.

The transmit/receive element 122 may be configured to transmit signalsto, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, thetransmit/receive element 122 may be an antenna configured to transmitand/or receive RF signals. In an embodiment, the transmit/receiveelement 122 may be an emitter/detector configured to transmit and/orreceive IR, UV, or visible light signals, for example. In yet anotherembodiment, the transmit/receive element 122 may be configured totransmit and/or receive both RF and light signals. It will beappreciated that the transmit/receive element 122 may be configured totransmit and/or receive any combination of wireless signals.

Although the transmit/receive element 122 is depicted in FIG. 1B as asingle element, the WTRU 102 may include any number of transmit/receiveelements 122. More specifically, the WTRU 102 may employ MIMOtechnology. Thus, in one embodiment, the WTRU 102 may include two ormore transmit/receive elements 122 (e.g., multiple antennas) fortransmitting and receiving wireless signals over the air interface 116.

The transceiver 120 may be configured to modulate the signals that areto be transmitted by the transmit/receive element 122 and to demodulatethe signals that are received by the transmit/receive element 122. Asnoted above, the WTRU 102 may have multi-mode capabilities. Thus, thetransceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, such as NR and IEEE 802.11, forexample.

The processor 118 of the WTRU 102 may be coupled to, and may receiveuser input data from, the speaker/microphone 124, the keypad 126, and/orthe display/touchpad 128 (e.g., a liquid crystal display (LCD) displayunit or organic light-emitting diode (OLED) display unit). The processor118 may also output user data to the speaker/microphone 124, the keypad126, and/or the display/touchpad 128. In addition, the processor 118 mayaccess information from, and store data in, any type of suitable memory,such as the non-removable memory 130 and/or the removable memory 132.The non-removable memory 130 may include random-access memory (RAM),read-only memory (ROM), a hard disk, or any other type of memory storagedevice. The removable memory 132 may include a subscriber identitymodule (SIM) card, a memory stick, a secure digital (SD) memory card,and the like. In other embodiments, the processor 118 may accessinformation from, and store data in, memory that is not physicallylocated on the WTRU 102, such as on a server or a home computer (notshown).

The processor 118 may receive power from the power source 134, and maybe configured to distribute and/or control the power to the othercomponents in the WTRU 102. The power source 134 may be any suitabledevice for powering the WTRU 102. For example, the power source 134 mayinclude one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion),etc.), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to the GPS chipset 136, which maybe configured to provide location information (e.g., longitude andlatitude) regarding the current location of the WTRU 102. In additionto, or in lieu of, the information from the GPS chipset 136, the WTRU102 may receive location information over the air interface 116 from abase station (e.g., base stations 114 a, 114 b) and/or determine itslocation based on the timing of the signals being received from two ormore nearby base stations. It will be appreciated that the WTRU 102 mayacquire location information by way of any suitablelocation-determination method while remaining consistent with anembodiment.

The processor 118 may further be coupled to other peripherals 138, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 138 may include anaccelerometer, an e-compass, a satellite transceiver, a digital camera(for photographs and/or video), a universal serial bus (USB) port, avibration device, a television transceiver, a hands free headset, aBluetooth® module, a frequency modulated (FM) radio unit, a digitalmusic player, a media player, a video game player module, an Internetbrowser, a Virtual Reality and/or Augmented Reality (VR/AR) device, anactivity tracker, and the like. The peripherals 138 may include one ormore sensors, the sensors may be one or more of a gyroscope, anaccelerometer, a hall effect sensor, a magnetometer, an orientationsensor, a proximity sensor, a temperature sensor, a time sensor; ageolocation sensor; an altimeter, a light sensor, a touch sensor, amagnetometer, a barometer, a gesture sensor, a biometric sensor, and/ora humidity sensor.

The WTRU 102 may include a full duplex radio for which transmission andreception of some or all of the signals (e.g., associated withparticular subframes for both the UL (e.g., for transmission) anddownlink (e.g., for reception) may be concurrent and/or simultaneous.The full duplex radio may include an interference management unit toreduce and or substantially eliminate self-interference via eitherhardware (e.g., a choke) or signal processing via a processor (e.g., aseparate processor (not shown) or via processor 118). In an embodiment,the WRTU 102 may include a half-duplex radio for which transmission andreception of some or all of the signals (e.g., associated withparticular subframes for either the UL (e.g., for transmission) or thedownlink (e.g., for reception)).

FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106according to an embodiment. As noted above, the RAN 104 may employ anE-UTRA radio technology to communicate with the WTRUs 102 a, 102 b, 102c over the air interface 116. The RAN 104 may also be in communicationwith the CN 106.

The RAN 104 may include eNode-Bs 160 a, 160 b, 160 c, though it will beappreciated that the RAN 104 may include any number of eNode-Bs whileremaining consistent with an embodiment. The eNode-Bs 160 a, 160 b, 160c may each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the eNode-Bs 160 a, 160 b, 160 c may implement MIMO technology. Thus,the eNode-B 160 a, for example, may use multiple antennas to transmitwireless signals to, and/or receive wireless signals from, the WTRU 102a.

Each of the eNode-Bs 160 a, 160 b, 160 c may be associated with aparticular cell (not shown) and may be configured to handle radioresource management decisions, handover decisions, scheduling of usersin the UL and/or DL, and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160 b, 160 c may communicate with one another over an X2 interface.

The CN 106 shown in FIG. 1C may include a mobility management entity(MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN)gateway (or PGW) 166. While each of the foregoing elements are depictedas part of the CN 106, it will be appreciated that any of these elementsmay be owned and/or operated by an entity other than the CN operator.

The MME 162 may be connected to each of the eNode-Bs 162 a, 162 b, 162 cin the RAN 104 via an S1 interface and may serve as a control node. Forexample, the MME 162 may be responsible for authenticating users of theWTRUs 102 a, 102 b, 102 c, bearer activation/deactivation, selecting aparticular serving gateway during an initial attach of the WTRUs 102 a,102 b, 102 c, and the like. The MME 162 may provide a control planefunction for switching between the RAN 104 and other RANs (not shown)that employ other radio technologies, such as GSM and/or WCDMA.

The SGW 164 may be connected to each of the eNode Bs 160 a, 160 b, 160 cin the RAN 104 via the S1 interface. The SGW 164 may generally route andforward user data packets to/from the WTRUs 102 a, 102 b, 102 c. The SGW164 may perform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when DL data is available forthe WTRUs 102 a, 102 b, 102 c, managing and storing contexts of theWTRUs 102 a, 102 b, 102 c, and the like.

The SGW 164 may be connected to the PGW 166, which may provide the WTRUs102 a, 102 b, 102 c with access to packet-switched networks, such as theInternet 110, to facilitate communications between the WTRUs 102 a, 102b, 102 c and IP-enabled devices.

The CN 106 may facilitate communications with other networks. Forexample, the CN 106 may provide the WTRUs 102 a, 102 b, 102 c withaccess to circuit-switched networks, such as the PSTN 108, to facilitatecommunications between the WTRUs 102 a, 102 b, 102 c and traditionalland-line communications devices. For example, the CN 106 may include,or may communicate with, an IP gateway (e.g., an IP multimedia subsystem(IMS) server) that serves as an interface between the CN 106 and thePSTN 108. In addition, the CN 106 may provide the WTRUs 102 a, 102 b,102 c with access to the other networks 112, which may include otherwired and/or wireless networks that are owned and/or operated by otherservice providers.

Although the WTRU is described in FIGS. 1A-1D as a wireless terminal, itis contemplated that in certain representative embodiments that such aterminal may use (e.g., temporarily or permanently) wired communicationinterfaces with the communication network.

In representative embodiments, the other network 112 may be a WLAN.

A WLAN in Infrastructure Basic Service Set (BSS) mode may have an AccessPoint (AP) for the BSS and one or more stations (STAs) associated withthe AP. The AP may have an access or an interface to a DistributionSystem (DS) or another type of wired/wireless network that carriestraffic in to and/or out of the BSS. Traffic to STAs that originatesfrom outside the BSS may arrive through the AP and may be delivered tothe STAs. Traffic originating from STAs to destinations outside the BSSmay be sent to the AP to be delivered to respective destinations.Traffic between STAs within the BSS may be sent through the AP, forexample, where the source STA may send traffic to the AP and the AP maydeliver the traffic to the destination STA. The traffic between STAswithin a BSS may be considered and/or referred to as peer-to-peertraffic. The peer-to-peer traffic may be sent between (e.g., directlybetween) the source and destination STAs with a direct link setup (DLS).In certain representative embodiments, the DLS may use an 802.11e DLS oran 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS)mode may not have an AP, and the STAs (e.g., all of the STAs) within orusing the IBSS may communicate directly with each other. The IBSS modeof communication may sometimes be referred to herein as an “ad-hoc” modeof communication.

When using the 802.11ac infrastructure mode of operation or a similarmode of operations, the AP may transmit a beacon on a fixed channel,such as a primary channel. The primary channel may be a fixed width(e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.The primary channel may be the operating channel of the BSS and may beused by the STAs to establish a connection with the AP. In certainrepresentative embodiments, Carrier Sense Multiple Access with CollisionAvoidance (CSMA/CA) may be implemented, for example in in 802.11systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, maysense the primary channel. If the primary channel is sensed/detectedand/or determined to be busy by a particular STA, the particular STA mayback off. One STA (e.g., only one station) may transmit at any giventime in a given BSS.

High Throughput (HT) STAs may use a 40 MHz wide channel forcommunication, for example, via a combination of the primary 20 MHzchannel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHzwide channel.

Very High Throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz,and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may beformed by combining contiguous 20 MHz channels. A 160 MHz channel may beformed by combining 8 contiguous 20 MHz channels, or by combining twonon-contiguous 80 MHz channels, which may be referred to as an 80+80configuration. For the 80+80 configuration, the data, after channelencoding, may be passed through a segment parser that may divide thedata into two streams. Inverse Fast Fourier Transform (IFFT) processing,and time domain processing, may be done on each stream separately. Thestreams may be mapped on to the two 80 MHz channels, and the data may betransmitted by a transmitting STA. At the receiver of the receiving STA,the above described operation for the 80+80 configuration may bereversed, and the combined data may be sent to the Medium Access Control(MAC).

Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. Thechannel operating bandwidths, and carriers, are reduced in 802.11af and802.11ah relative to those used in 802.11n, and 802.11ac. 802.11afsupports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space(TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and16 MHz bandwidths using non-TVWS spectrum. According to a representativeembodiment, 802.11ah may support Meter Type Control/Machine-TypeCommunications, such as MTC devices in a macro coverage area. MTCdevices may have certain capabilities, for example, limited capabilitiesincluding support for (e.g., only support for) certain and/or limitedbandwidths. The MTC devices may include a battery with a battery lifeabove a threshold (e.g., to maintain a very long battery life).

WLAN systems, which may support multiple channels, and channelbandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include achannel which may be designated as the primary channel. The primarychannel may have a bandwidth equal to the largest common operatingbandwidth supported by all STAs in the BSS. The bandwidth of the primarychannel may be set and/or limited by a STA, from among all STAs inoperating in a BSS, which supports the smallest bandwidth operatingmode. In the example of 802.11ah, the primary channel may be 1 MHz widefor STAs (e.g., MTC type devices) that support (e.g., only support) a 1MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.Carrier sensing and/or Network Allocation Vector (NAV) settings maydepend on the status of the primary channel. If the primary channel isbusy, for example, due to a STA (which supports only a 1 MHz operatingmode), transmitting to the AP, the entire available frequency bands maybe considered busy even though a majority of the frequency bands remainsidle and may be available.

In the United States, the available frequency bands, which may be usedby 802.11ah, are from 902 MHz to 928 MHz. In Korea, the availablefrequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the availablefrequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidthavailable for 802.11ah is 6 MHz to 26 MHz depending on the country code.

FIG. 1D is a system diagram illustrating the RAN 113 and the CN 115according to an embodiment. As noted above, the RAN 113 may employ an NRradio technology to communicate with the WTRUs 102 a, 102 b, 102 c overthe air interface 116. The RAN 113 may also be in communication with theCN 115.

The RAN 113 may include gNBs 180 a, 180 b, 180 c, though it will beappreciated that the RAN 113 may include any number of gNBs whileremaining consistent with an embodiment. The gNBs 180 a, 180 b, 180 cmay each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the gNBs 180 a, 180 b, 180 c may implement MIMO technology. For example,gNBs 180 a, 108 b may utilize beamforming to transmit signals to and/orreceive signals from the gNBs 180 a, 180 b, 180 c. Thus, the gNB 180 a,for example, may use multiple antennas to transmit wireless signals to,and/or receive wireless signals from, the WTRU 102 a. In an embodiment,the gNBs 180 a, 180 b, 180 c may implement carrier aggregationtechnology. For example, the gNB 180 a may transmit multiple componentcarriers to the WTRU 102 a (not shown). A subset of these componentcarriers may be on unlicensed spectrum while the remaining componentcarriers may be on licensed spectrum. In an embodiment, the gNBs 180 a,180 b, 180 c may implement Coordinated Multi-Point (CoMP) technology.For example, WTRU 102 a may receive coordinated transmissions from gNB180 a and gNB 180 b (and/or gNB 180 c).

The WTRUs 102 a, 102 b, 102 c may communicate with gNBs 180 a, 180 b,180 c using transmissions associated with a scalable numerology. Forexample, the OFDM symbol spacing and/or OFDM subcarrier spacing may varyfor different transmissions, different cells, and/or different portionsof the wireless transmission spectrum. The WTRUs 102 a, 102 b, 102 c maycommunicate with gNBs 180 a, 180 b, 180 c using subframe or transmissiontime intervals (TTIs) of various or scalable lengths (e.g., containingvarying number of OFDM symbols and/or lasting varying lengths ofabsolute time).

The gNBs 180 a, 180 b, 180 c may be configured to communicate with theWTRUs 102 a, 102 b, 102 c in a standalone configuration and/or anon-standalone configuration. In the standalone configuration, WTRUs 102a, 102 b, 102 c may communicate with gNBs 180 a, 180 b, 180 c withoutalso accessing other RANs (e.g., such as eNode-Bs 160 a, 160 b, 160 c).In the standalone configuration, WTRUs 102 a, 102 b, 102 c may utilizeone or more of gNBs 180 a, 180 b, 180 c as a mobility anchor point. Inthe standalone configuration, WTRUs 102 a, 102 b, 102 c may communicatewith gNBs 180 a, 180 b, 180 c using signals in an unlicensed band. In anon-standalone configuration WTRUs 102 a, 102 b, 102 c may communicatewith/connect to gNBs 180 a, 180 b, 180 c while also communicatingwith/connecting to another RAN such as eNode-Bs 160 a, 160 b, 160 c. Forexample, WTRUs 102 a, 102 b, 102 c may implement DC principles tocommunicate with one or more gNBs 180 a, 180 b, 180 c and one or moreeNode-Bs 160 a, 160 b, 160 c substantially simultaneously. In thenon-standalone configuration, eNode-Bs 160 a, 160 b, 160 c may serve asa mobility anchor for WTRUs 102 a, 102 b, 102 c and gNBs 180 a, 180 b,180 c may provide additional coverage and/or throughput for servicingWTRUs 102 a, 102 b, 102 c.

Each of the gNBs 180 a, 180 b, 180 c may be associated with a particularcell (not shown) and may be configured to handle radio resourcemanagement decisions, handover decisions, scheduling of users in the ULand/or DL, support of network slicing, dual connectivity, interworkingbetween NR and E-UTRA, routing of user plane data towards User PlaneFunction (UPF) 184 a, 184 b, routing of control plane informationtowards Access and Mobility Management Function (AMF) 182 a, 182 b andthe like. As shown in FIG. 1D, the gNBs 180 a, 180 b, 180 c maycommunicate with one another over an Xn interface.

The CN 115 shown in FIG. 1D may include at least one AMF 182 a, 182 b,at least one UPF 184 a,184 b, at least one Session Management Function(SMF) 183 a, 183 b, and possibly a Data Network (DN) 185 a, 185 b. Whileeach of the foregoing elements are depicted as part of the CN 115, itwill be appreciated that any of these elements may be owned and/oroperated by an entity other than the CN operator.

The AMF 182 a, 182 b may be connected to one or more of the gNBs 180 a,180 b, 180 c in the RAN 113 via an N2 interface and may serve as acontrol node. For example, the AMF 182 a, 182 b may be responsible forauthenticating users of the WTRUs 102 a, 102 b, 102 c, support fornetwork slicing (e.g., handling of different PDU sessions with differentrequirements), selecting a particular SMF 183 a, 183 b, management ofthe registration area, termination of NAS signaling, mobilitymanagement, and the like. Network slicing may be used by the AMF 182 a,182 b in order to customize CN support for WTRUs 102 a, 102 b, 102 cbased on the types of services being utilized WTRUs 102 a, 102 b, 102 c.For example, different network slices may be established for differentuse cases such as services relying on ultra-reliable low latency (URLLC)access, services relying on enhanced massive mobile broadband (eMBB)access, services for machine type communication (MTC) access, and/or thelike. The AMF 162 may provide a control plane function for switchingbetween the RAN 113 and other RANs (not shown) that employ other radiotechnologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP accesstechnologies such as WiFi.

The SMF 183 a, 183 b may be connected to an AMF 182 a, 182 b in the CN115 via an N11 interface. The SMF 183 a, 183 b may also be connected toa UPF 184 a, 184 b in the CN 115 via an N4 interface. The SMF 183 a, 183b may select and control the UPF 184 a, 184 b and configure the routingof traffic through the UPF 184 a, 184 b. The SMF 183 a, 183 b mayperform other functions, such as managing and allocating WTRU IPaddress, managing PDU sessions, controlling policy enforcement and QoS,providing downlink data notifications, and the like. A PDU session typemay be IP-based, non-IP based, Ethernet-based, and the like.

The UPF 184 a, 184 b may be connected to one or more of the gNBs 180 a,180 b, 180 c in the RAN 113 via an N3 interface, which may provide theWTRUs 102 a, 102 b, 102 c with access to packet-switched networks, suchas the Internet 110, to facilitate communications between the WTRUs 102a, 102 b, 102 c and IP-enabled devices. The UPF 184, 184 b may performother functions, such as routing and forwarding packets, enforcing userplane policies, supporting multi-homed PDU sessions, handling user planeQoS, buffering downlink packets, providing mobility anchoring, and thelike.

The CN 115 may facilitate communications with other networks. Forexample, the CN 115 may include, or may communicate with, an IP gateway(e.g., an IP multimedia subsystem (IMS) server) that serves as aninterface between the CN 115 and the PSTN 108. In addition, the CN 115may provide the WTRUs 102 a, 102 b, 102 c with access to the othernetworks 112, which may include other wired and/or wireless networksthat are owned and/or operated by other service providers. In oneembodiment, the WTRUs 102 a, 102 b, 102 c may be connected to a localData Network (DN) 185 a, 185 b through the UPF 184 a, 184 b via the N3interface to the UPF 184 a, 184 b and an N6 interface between the UPF184 a, 184 b and the DN 185 a, 185 b.

In view of FIGS. 1A-1D, and the corresponding description of FIGS.1A-1D, one or more, or all, of the functions described herein withregard to one or more of: WTRU 102 a-d, Base Station 114 a-b, eNode-B160 a-c, MME 162, SGW 164, PGW 166, gNB 180 a-c, AMF 182 a-b, UPF 184a-b, SMF 183 a-b, DN 185 a-b, and/or any other device(s) describedherein, may be performed by one or more emulation devices (not shown).The emulation devices may be one or more devices configured to emulateone or more, or all, of the functions described herein. For example, theemulation devices may be used to test other devices and/or to simulatenetwork and/or WTRU functions.

The emulation devices may be designed to implement one or more tests ofother devices in a lab environment and/or in an operator networkenvironment. For example, the one or more emulation devices may performthe one or more, or all, functions while being fully or partiallyimplemented and/or deployed as part of a wired and/or wirelesscommunication network in order to test other devices within thecommunication network. The one or more emulation devices may perform theone or more, or all, functions while being temporarilyimplemented/deployed as part of a wired and/or wireless communicationnetwork. The emulation device may be directly coupled to another devicefor purposes of testing and/or may performing testing using over-the-airwireless communications.

The one or more emulation devices may perform the one or more, includingall, functions while not being implemented/deployed as part of a wiredand/or wireless communication network. For example, the emulationdevices may be utilized in a testing scenario in a testing laboratoryand/or a non-deployed (e.g., testing) wired and/or wirelesscommunication network in order to implement testing of one or morecomponents. The one or more emulation devices may be test equipment.Direct RF coupling and/or wireless communications via RF circuitry(e.g., which may include one or more antennas) may be used by theemulation devices to transmit and/or receive data.

New radio (NR) may be operable with current and future mobile wirelesscommunications systems. NR use cases may include, for example, eMBB,Ultra High Reliability and Low Latency Communications (URLLC) andmassive Machine Type Communications (mMTC). NR may support transmissionin high frequency bands, such as centimeter-wave (cm-wave) and/ormillimeter-wave (mm-wave) frequencies. Operation in cm-wave and/ormm-wave frequency bands may present propagation-related challenges,e.g., in view of higher path loss and shadowing.

High-reliability services may be supported, for example, by very lowblock error rates, e.g., of the order of 0.001%. Lower error rates maybe achieved, for example, with higher reliability for physical layercontrol information (e.g., hybrid automatic request acknowledgement(HARQ-ACK), uplink grants and downlink assignments). In an example(e.g., for HARQ-ACK) a probability of misinterpreting a NACK as an ACKat a level of 0.1% may be adequate for some (e.g., general) mobilebroadband services, but may be too large, for example, forultra-reliable services (e.g., since a negative-acknowledgement (NACK)to acknowledgement (ACK) misinterpretation event may result in loss of atransport block).

A WTRU may be configured for multiple concurrent transmissions. NR maysupport a WTRU configuration that may include one or more cells for agiven MAC entity and/or for multiple MAC entities. A configuration ofone cell may provide single cell operation. A configuration of multiplecells may provide carrier aggregation (CA), for example, NR CAoperation. A configuration of multiple MAC entities may include dualconnectivity (DC) for NR (NR DC). A configuration of multiple MACentities may provide combination of LTE and NR (e.g., evolved UMTSterrestrial radio access network (E-UTRAN) New Radio—Dual Connectivity(EN-DC)). NR may provide a WTRU configuration comprising a cellconfigured with one downlink carrier, one uplink carrier, and asupplementary uplink carrier (SUL). NR may support a cell configuredwith one or more bandwidth part(s) (BWPs). A BWP may be characterized byat least one of a frequency location (e.g., a center frequency and/or afrequency bandwidth), or a numerology.

For EN-DC, NR CA and NR DC in licensed bands, various combinations(e.g., different combinations) of carriers may introduce various timingrelationships (e.g., different timing relationships) betweentransmissions associated with a WTRU (or between transmissions that mayat least partly overlap in time) in terms one or more of numerology,transmission start time, or transmission duration. For example, each ofthe configured component carriers (downlink (DL) and/or uplink (UL))and/or bandwidth parts (BWPs) (DL and/or UL) for a WTRU may have thesame or different numerology, and overlapping transmissions betweendifferent component carriers/BWPs may have the same or differentstarting time; and the same or different physical uplink shared channel(PUSCH)/physical uplink control channel (PUCCH) transmission duration.

Timing and/or scheduling aspects may be provided, for example, in caseof asynchronous transmissions and/or in cases of partial and/or completeoverlapping between different uplink transmissions associated with aWTRU. In an example, different transmissions may operate with differentHARQ timelines, for example, based on dynamic scheduling information.For example, such scheduling information may include dynamicallyvariable scheduling-related delay components. The dynamically variablescheduling-related delay components may be provided via downlink controlinformation (DCI)). The scheduling-related delay components may includeone or more of K1, K2, N1, or N2. K1 may be a delay between a downlink(DL) data (PDSCH) reception and its corresponding ACK transmission onuplink (UL). K2 may be a delay between an UL grant reception in DL andan UL data transmission (e.g., PUSCH transmission). N1 may be a numberof OFDM symbols used for a WTRU processing from the end of NR-PDSCHreception to the earliest possible start of the corresponding ACK/NACKtransmission, for example, from the WTRU perspective. N2 may be a numberof OFDM symbols used for a WTRU processing from the end of NR-PDCCHcomprising the UL grant reception to the earliest possible start of thecorresponding NR-PUSCH transmission, for example, from the WTRUperspective.

A scheduler may adjust an error probability of control information, forexample, by selecting transmission power parameters (e.g., associatedwith an uplink transmission) and/or aggregation level (e.g., associatedwith a downlink transmission). Achieving very low error rates may beproblematic.

In an example, very low error rates may not be attained by parameteradjustment using transmission techniques, for example, in presence ofbursty interference and/or other channel impairments (e.g., severeshadowing at mm-wave frequencies).

Spectrum efficiency and user throughput may be severely degraded, forexample, when operating at very low error rates, as significantly moreresources (time, frequency, and/or power) may be consumed than whenoperating at typical error rates, when such techniques are applied toone or more types of transmissions. Differentiated processing betweenultra-reliable transmissions and other transmissions (e.g., by resourcesegregation) may be less efficient, e.g., given that ultra-reliabletraffic may be bursty.

Very low error rates (e.g., for ultra-reliable services) may beachieved. Efficient operation (e.g., in a system and/or a WTRU) withultra-reliable and other (e.g., non-ultra reliable) mobile broadbanddata traffic may be achieved.

Uplink control information (UCI) may comprise, for example, HARQfeedback information (e.g., HARQ-ACK), scheduling request (SR), and/orchannel state information (CSI). UCI may be transmitted over an uplinkcontrol channel (e.g., physical uplink control channel (PUCCH)), and/orover an uplink data channel (e.g., physical uplink shared channel(PUCCH)). UCI may be transmitted with or without multiplexing withuplink data. HARQ feedback information (e.g., HARQ-ACK) may pertain totransport block(s), code block(s) and/or code block group(s).

Downlink control information (DCI) may refer to physical controlsignaling that may be received from a network (e.g., uplink grants,downlink assignments, power control commands, slot format indicators,HARQ information and so on). DCI may be transmitted, for example, over adownlink control channel (e.g., PDCCH) (e.g., in a common orWTRU-specific search space or over a group-common control channel (e.g.,on PDCCH)). A PDCCH may be mapped to resources of a control resource set(CORESET). A WTRU may attempt decoding PDCCH, for example, from one ormore search spaces within a CORESET. A WTRU may be configured, forexample, with at least one CORESET.

DCI diversity may be provided. In an example, transmission reliabilityof DCI may be increased, for example, by transmission of multiple DCIinstances over resources separated in time, frequency, and/or spacedomains. Multiple instances may provide a diversity gain againstshort-term fading, long-term fading, and/or interference.

A DCI (e.g., each DCI instance) may be transmitted over a downlinkphysical control channel (e.g., PDCCH, group-common PDCCH, PHICH and soon). An instance may be transmitted over PDSCH (e.g., when DCI on PDSCHmay be supported). A PDCCH (e.g., each PDCCH) may be received based on aCORESET that may be configured by higher layers. A configuration mayinclude one or more parameters. For example, a configuration may includea component carrier or a serving cell, one or more bandwidth parts(BWPs), a subset of resource blocks within a BWP (e.g., each BWP), a setof time symbols within a slot or a mini-slot, a sub-carrier spacing, asubset of slots within a subframe, and/or one or more reference signals(e.g., CSI-RS). An independent configuration of one or more parametersmay provide diversity in time, frequency, and/or space. In an example,frequency diversity may be provided (e.g., by configuring differentcomponent carriers or BWPs between CORESETs) with or without providingspace and/or time diversity (e.g., by configuring different sets of timesymbols and/or different reference signals).

DCI diversity may be configurable. For example, DCI diversity may beactivated or de-activated. The activation or deactivation of DCIdiversity, for example, may be based on MAC layer signaling or physicallayer signaling. In an example, a WTRU may receive an activation commandbased on a first CORESET to initiate monitoring of a second DCI instanceon a second CORESET. A WTRU may receive a de-activation command formonitoring a DCI instance on a specific CORESET.

DCI diversity may be applied. Contents of a DCI instance (e.g., each DCIinstance) may be set according to one or more of the following: (i) samecontents transmitted over a multiple DCI instances (e.g., repetition);(ii) same contents transmitted over multiple DCI instances (e.g., blockencoding), or (iii) nature of contents.

In an example, each of the multiple DCI instances may include and encodethe same information bits for at least one type or format of DCI (e.g.,HARQ-ACK for PUSCH, PDSCH assignment, PUSCH grant). A DCI may bedecodable (e.g., completely decodable) from the reception of an instance(e.g., a single instance).

In an example, a DCI may be encoded, for example, by segmenting the DCIinto N blocks and encoding the DCI into D blocks. In an example, adecoding of at least N of the D DCI instances (e.g., at a receiver) maybe sufficient to recover the entirety of the DCI. In an example,encoding may consist of a parity code.

In an example, DCI instances may include one or more of the following:information associated with at least one DL data transmission overPDSCH, or information associated with at least one UL data transmissionover PUSCH.

In an example, a WTRU may be configured to monitor PDCCH over multipleCORESETs (e.g., two CORESETs). The WTRU may monitor the PDCCH ondifferent carriers or bandwidth parts. A WTRU may receive, for example,multiple DCI instances (e.g., up to two DCI instances). In an example,the DCI instances may include the same information received by the WTRUvia PDCCH in multiple carriers (e.g., each carrier may be received on acarrier, in a multiple DCI case). Information on a DCI (e.g., each DCI)may include PDSCH (or PUSCH) assignments/grants for multiple carriers(e.g., both carriers). A WTRU may receive PDSCH or transmit PUSCH onmultiple carriers (e.g., both carriers), for example, even in a casewhen a (e.g., one) of the DCI instances may not be successfully decoded.Very low BLER may be achieved with low latency, for example, when themultiple PSDCH transmissions (e.g., both PDSCH transmissions) or PUSCHtransmissions may be encoded into the same transport block, e.g., sincethe DCI and the data may be (e.g., are) independently protected bydiversity, as illustrated by example in FIG. 2. As illustrated in FIG.2, DCI on downlink component carrier 1 (DL CC1) 202 and the DCI on thedownlink component carrier 2 (DL CC2) 204 may have same contents. Forexample, each of the DCI may include information associated with PDSCH206 and PSDCH 208.

A DCI index may be provided. In an example, a DCI instance (e.g., eachDCI instance) may include a field (e.g., DCI index) that may identifyDCI contents. A WTRU may discard DCI instances that may include the sameinformation. The duplicate DCIs may be discarded to reduce processing.In an example, a WTRU may receive a first DCI instance with a firstvalue of the DCI index. A WTRU may receive subsequent DCI instances thatmay include the same value of the DCI index (e.g., within a set ofCORESETs over which DCI diversity may be configured within a timeperiod). A WTRU may (e.g., upon receipt) discard the subsequent DCIinstances. A WTRU may use a DCI index, for example, to differentiatebetween a diversity DCI and a DCI that may include new information.

UCI diversity may be provided. Transmission reliability of UCI may beincreased, for example, by transmission of multiple instances overresources that may be separated in one or more of the following: time,frequency, or space domains. Multiple UCI instances may, for example,provide a diversity gain against short-term fading, long-term fading,and/or interference. A UCI instance (e.g., each UCI instance) may betransmitted over a physical uplink control channel (PUCCH) or a physicaluplink shared channel (PUCCH). In an example, UCI diversity may beapplicable to certain types of UCI (e.g., HARQ-ACK).

In an example, UCI instances may be transmitted over multiple carriersand/or bandwidth parts, a WTRU may be configured to operate on. Asillustrated in FIG. 3, the same HARQ-ACK information that may pertain toa downlink assignment (e.g., received in a previous slot 302) may betransmitted over multiple PUCCH instances (e.g., two PUCCH instances 306and 308). The two PUCCH instances may be include a first UCI instance306 that may be transmitted on an UL component carrier one (CC1) 310 anda second UCI instance 308 that may be transmitted on UL componentcarrier two (CC2) 312. The UCI may be transmitted in slot 2 304. Each ofthe first UCI instance 306 and the second UCI instance 308 may includesimilar information (e.g., same HARQ ACK-NACK information).

FIG. 3 is an example of implementing a DCI diversity and a UCIdiversity. In an example, a UCI instance (e.g., each UCI instances) mayinclude transmission of an OFDM symbol (e.g., a single OFDM symbol) inadjacent symbols (e.g., using short PUCCH format). Other examples in thetime domain may include, for example, transmission in the same OFDMsymbol or transmission in different slots. Resources (e.g., RB, timesymbol, slot, etc.) that may be occupied by a UCI instance (e.g., eachUCI instance) may be configured independently.

In an example, UCI instances may be transmitted over multiple beams. Forexample, multiple beams may be transmitted using different pre-coders. AWTRU may be configured for beam determination associated with a UCIinstance (e.g., each UCI instance). The WTRU may be configured withinformation including one or more of the following: a beam index, a beamprocess identity, an SRS indicator, or a CSI-RS indicator (e.g., whenbeam correspondence exists), etc. Information used by the WTRU for beamdetermination (e.g., for PUCCH) may be configured by higher layers for aUCI instance (e.g., each UCI instance) or may be indicated in a DCI thatmay include an ACK/NACK resource indicator (ARI). Information used bythe WTRU for beam determination (e.g., for PUSCH) may be indicated via aDCI that may include a grant associated with a beam.

Information used by the WTRU for beam determination may be derived(e.g., implicitly derived) from a PDCCH that may include an assignment.In an example, a beam associated with transmission of a PUCCH instancemay be derived from a reference signal (e.g., a channel stateinformation reference signal (CSI-RS)) or a beam indicator that may beassociated with a control resource set or a PDCCH transmission that mayinclude an assignment. This approach may be used, for example, whenPDCCH diversity (or the DCI diversity) may be used in addition to theUCI diversity. A WTRU may transmit a PUCCH instance (e.g., one PUCCHinstance) for a received PDCCH instance (e.g., each received PDCCHinstance). The PDCCH instance may include an assignment, for example,when and or how UCI may be transmitted over PUCCH.

A Supplementary Uplink (SUL) may be provided. In an example, a WTRU maybe configured with a SUL carrier for at least one serving cell. The WTRUmay be configured to transmit UCI including, for example, a schedulingrequest (SR), channel state information (CSI), or an HARQ ACK/NACK. UCImay be transmitted over the regular UL carrier and the SUL carrierassociated with the serving cell.

UCI diversity may be applied. Contents of a UCI instance (e.g., each UCIinstance) may be set, for example, according to one or more of the: (i)whether same contents are to be transmitted over each of the multipleUCI instances (e.g., repetition); (ii) whether same contents are to betransmitted over UCI instances (e.g., block encoding); or (iii) natureof contents.

In an example, a UCI instance (e.g., each UCI instance) may include andencode same information bits for at least one type of UCI (e.g.,HARQ-ACK). A UCI may be decodable from the reception of a singleinstance. In an example, a UCI may be encoded, for example, bysegmenting the UCI into N blocks and encoding the segmented N blocksinto D blocks. In an example, decoding of at least N blocks of the D UCIinstances at a receiver may be sufficient to recover the entirety of theUCI. In an example, encoding may include a parity code.

In an example (e.g., where DCI diversity may not be applied), a UCI mayinclude a set of HARQ-ACK bits. An association between a specificHARQ-ACK bit and a reception outcome of a transport block may bedetermined, for example, based on a downlink assignment index.

In an example (e.g., where DCI diversity may be applied), a set ofHARQ-ACK bits may be generated and transmitted, for example, for each ofthe DCI instances that may be configured to be received in diversity(e.g., based on the same contents). This may occur, for example,irrespective of whether a DCI instance may be successfully decoded. AWTRU may report NACK for transport blocks corresponding to a DCIinstance that may not be received, for example, when the WTRU may beconfigured to receive multiple DCI instances (e.g., two DCI instances)in diversity, but receives fewer than the configured DCI instances(e.g., configured two DCI instances). Reporting may be performed, forexample, when a WTRU receives at least one DCI instance. A network maybe allowed to determine missed assignments from a DCI instance (e.g.,each DCI instance). Determination of missed assignments may be usefulfor link adaptation of PDCCH.

In an example, DCI diversity may be applied. A WTRU may report a set ofHARQ-ACK bits for a set of DCI instances that may be configured to bereceived in diversity, for example, when the WTRU receives at least oneDCI instance. A WTRU may report an indication of a subset of DCIinstances that may be successfully decoded within a set of DCI instancesin diversity.

A WTRU may receive more than one DCIs that may indicate DL data for thesame HARQ process and transport block(s). The DCIs may be encoded usingdifferent redundancy versions. A WTRU may report one HARQ-ACK bit pertransport block (e.g., irrespective of the number of received instancesof PDSCH that may include data for the transport block). A WTRU maytransmit a HARQ-ACK bit per transport block and a PDSCH instance thatmay include data of the transport block (e.g., with the same value).

Power control with UCI diversity may be provided. Transmission powerassociated with a transmission (e.g., a PUCCH transmission or a PUSCHtransmission) may be set independently, for example, when UCI diversityis applied. For example, a separate configuration of one or morereference signals may be used for path loss estimation and otherparameters may be used to determine transmission power.

Power control with UCI diversity for determination of transmit powercontrol (TPC) may be provided. A WTRU may determine a TPC command thatmay be applicable to a transmission for which UCI diversity may beapplied.

In an exemplary determination of TPC, a WTRU may apply similar TPCadjustment to each of the multiple UCI instance transmissions. A TPCadjustment may be received, for example, from a DCI that may beassociated with a UCI transmission. For example, a DCI may include a DLassignment or a CSI request.

In an exemplary determination of TPC, a WTRU may apply a separate TPCadjustment to each of the multiple UCI instance transmissions. A TPCadjustment (e.g., each TPC adjustment) may be received, for example, viaa DCI that may be associated with a UCI transmission. In an example, anassociated DCI may include two TPC adjustment values, for example, whena UCI diversity may be configured using two transmissions.

In an exemplary determination of TPC, a WTRU may apply a separate TPCadjustment to each of the UCI instance transmissions. A TPC adjustmentmay be received for each of the UCI instances, for example, via aspecific DCI instance that may be associated with the UCI instance.

Power control with power control modes, for example, for carrieraggregation (CA) and/or dual connectivity (DC) may be provided. In anexample, a WTRU may apply a priority level to a transmission that mayinclude UCI, for example, when UCI diversity is activated. The WTRU mayapply the priority level, for example, if configured with a powercontrol mode (PCM). The WTRU may be configured to group one or moretype(s) of transmission(s). The WTRU may be configured to allocate atleast an amount (e.g., a fraction) of the total WTRU available power toa group of transmissions e.g., with a minimum guaranteed power. The WTRUmay determine that transmissions that include UCI are part of a samegroup of transmissions. The WTRU may perform such grouping, for example,if the UCI is associated with a transmission profile. For example, suchtransmission profile may correspond to an ultra-reliable low latencycommunications (URLLC) type of transmission. The WTRU may assign ahigher priority to such group of transmissions than other datatransmissions (e.g., data transmissions associated with a transmissionprofile that corresponds to non-URLLC type of transmission). In a WTRUconfigured with CA, for example, a transmission that includes at leastsome UCI generated when applying UCI diversity may have highest priorityover other transmissions for a given MAC instance. For a WTRU configuredwith DC and/or with multiple groups of transmissions, for example, agroup of transmissions (or a cell group) with at least one transmissionincluding at least some UCI (generated, e.g., when applying UCIdiversity) may have highest priority than other group(s).

Resource allocation may be provided with UCI diversity using PUCCH. Aresource and format of a PUCCH transmission may be determined (e.g.,when a UCI instance is transmitted over PUCCH), for example, accordingto one or more example procedures. In an example, a WTRU may beconfigured with one or more combinations of PUCCH resources. A PUCCHresource (e.g., each PUCCH resource) may correspond to a resource overwhich a UCI instance may be transmitted. In an example (e.g., with twoUCI instances), a combination may be defined as PUCCH resource index #24on a first CC or bandwidth part and PUCCH resource index #13 on a secondCC or bandwidth part. A combination may be referred to as a PUCCHdiversity resource or PUCCH diversity super-resource. A WTRU may beconfigured (e.g., by higher layers) with more than one PUCCH diversityresource. The PUCCH diversity resource may be indicated in a field(e.g., ARI field) of an associated DCI. A WTRU may be configured (e.g.,by higher layers) with a pool. The pool may include normal PUCCHresources and PUCCH diversity resources that may allow a network tocontrol (e.g., dynamically control) the use of UCI diversity.

In an example, a WTRU may be configured with DCI diversity in additionto UCI diversity. A WTRU may transmit a UCI instance on a resource thatmay be indicated by an associated DCI instance. A DCI instance (e.g.,each DCI instance) may comprise an ARI that may indicate a PUCCHresource. A WTRU may transmit a UCI instance, for example, when the WTRUmay have received a corresponding DCI instance.

Transmission of DTX feedback may be provided. In an example, a WTRU maytransmit HARQ-ACK information in a specific PUCCH resource. The HARQ-ACKmay indicate (e.g., explicitly indicate) that a DL transmission or a DLassignment was not received (e.g., in case of discontinuous transmission(DTX)) from a specific CORESET at a given slot or mini-slot. The timingof a PUCCH resource may be obtained, for example, from a timing of theslot or mini-slot where a DL assignment was not received.

PUCCH interference randomization may be provided. In an example, a PUCCHtransmission from two or more WTRUs to two or moretransmission/reception points (TRPs) may collide. Interferencerandomization may be used, for example, to reduce the effect of a stronginterfering PUCCH transmission on a victim PUCCH transmission.Interference randomization may be used, for example, by a pair of WTRUsto not use colliding PUCCH resources.

Interference randomization may be utilized to increase transmissiondiversity. Interference randomization may include, for example, one ormore of the following hopping resources: hopping a transmission beam orbeam pair, hopping PUCCH symbols within a slot or across slots, orhopping a duplication pattern.

In an example of hopping resources, hopping may be performed within aBWP or across multiple BWPs. A PUCCH transmission (e.g., each PUCCHtransmission) may, for example, cycle over a pattern of frequencyresources. In an example, hopping may be performed within a PUCCHtransmission.

In an example of hopping a transmission beam or beam pair, PUCCHtransmissions may cycle among a set of beams. In an example, cyclingamong beams may be performed, for example, using a beam per set of PUCCHsymbols within a PUCCH transmission. In an example of hopping PUCCHsymbols within a slot or across slots, a short PUCCH may occupydifferent symbols of a slot for each of the multiple PUCCHtransmissions.

In an example of hopping a duplication pattern, a PUCCH transmission(e.g., each PUCCH transmission) may use multiple duplications. Each ofthe duplications may use different resources. A subsequent PUCCHtransmission (e.g., each subsequent PUCCH transmission) may use adifferent set (e.g., a distinct set) of resources. The different sets ofresources may be used to enable multiple duplications.

Use of interference randomization and/or hopping patterns may beindicated to a WTRU. For example, such use of interference randomizationand/or hopping patterns may be indicated dynamically to a WTRU. Hoppingpatterns may be determined, for example, based on a property of a PUCCHtransmission. In an example, a hopping PUCCH configuration may depend ona frame timing, a subframe timing or a slot timing of the PUCCH. In anexample, a PUCCH configuration may depend on a PUCCH configuration usedfor a previous PUCCH transmission. In an example, a hopping PUCCHconfiguration may depend on a WTRU parameter (e.g., WTRU ID) or a TRPparameter (e.g., TRP ID).

Configuration of PUCCH resources may be provided. A WTRU may beconfigured to use one or more PUCCH formats or format types (e.g., ashort PUCCH or a long PUCCH). A WTRU may be configured with parametersassociated with one or more PUCCH formats. A configuration of PUCCHresources may be provided, for example, provided semi-statically.

A configuration of PUCCH resources may include, for example, one or moreof: (i) a PUCCH format (e.g., a short PUCCH format or a long PUCCHformat); (ii) a PUCCH duration in symbols (e.g., 1 or 2 symbol shortPUCCH and duration of long PUCCH); (iii) a waveform used for PUCCHtransmission (e.g., cyclic prefix based orthogonal frequency divisionmultiplexing (CP-OFDM) or discrete Fourier transform spread orthogonalfrequency division multiplexing (DFT-s-OFDM)); (iv) a numerology usedfor PUCCH (e.g., a subcarrier spacing, a CP type, etc.); (v) a timelocation (e.g., a symbol location within a slot where PUCCH may betransmitted); (vi) a frequency location (e.g., subcarriers, PRBs,BandWidth Part (BWP)); (vii) a frequency interlace index (e.g., used toenable FDM of multiple PUCCH on the same PRB or BWP, where a PUCCHtransmission may be assigned to one or more interlace within a PRB orBWP); (viii) hopping pattern(s) (e.g., for hopping within a PUCCHtransmission or across PUCCH transmissions); (ix) a beam or a beam pair;(x) a duplication pattern (e.g., for a PUCCH transmission that may beduplicated across multiple resources); (xi) an Orthogonal Cover Code(OCC) (e.g., may include whether the OCC applies over time or subcarrierelements); (xii) a cyclic shift; or (xiii) a transmit diversity scheme.

A frequency location may include, for example, a frequency allocationwhere a PUCCH may be transmitted. The frequency location may beprovided, for example, as an offset value. An offset may be applied, forexample, to a frequency location of a PDCCH that may configure a PUCCH,or a PDCCH assigning a PDSCH, or a PDSCH. An offset may be applied to afrequency location of a concurrent PUSCH. A frequency location mayinclude, for example, a set of subcarriers, PRBs, and/or BWPs. A set maybe used to indicate (e.g., dynamically indicate) a frequency locationfor a PUCCH transmission instance (e.g., each PUCCH transmissioninstance). A set may be used, for example, to enable frequency diversityvia repetition. A set may be used, for example, to enable frequencyhopping.

A configuration (e.g., including a duplication pattern) may include aset of resources over which a PUCCH transmission may be duplicated.Different duplication patterns may be selected (e.g., dynamicallyselected).

A semi-static configuration may include one or more tables. A table mayinclude a set of codepoints and a set of PUCCH configurations that maybe tied to each codepoint in the set of codepoints. In an example, afirst table may include configurations for short PUCCH transmissions anda second table may include configurations for long PUCCH transmissions.In an example, a table may be applicable to multiple PUCCH durations andPUCCH formats.

A dynamic indication of PUCCH configuration may be provided. In anexample, an indication (e.g., a dynamic indication) may be provided(e.g., to a WTRU) indicating a combination of PUCCH configurations totransmit UCI, such as HARQ A/N or CSI. A dynamic indication may include,for example, a table index and a codepoint index to be used within thetable. In an example, a dynamic indication may be provided (e.g.,implicitly provided). For example, the dynamic indication may beprovided as a function of a transmission (e.g., as a function of aparameter of a PDCCH transmission or a PDSCH transmission). In anexample, a hybrid procedure may be used. A WTRU may determine a PUCCHconfiguration, for example, based on a combination of an explicit indexand an implicit relationship. In an example, a WTRU may determine aPUCCH configuration dynamically. In an example, a WTRU may determine afirst set of configurations or a PUCCH configuration table and maydetermine a second set of configurations or a codepoint within a table.For example, the PUCCH configuration table may be determined implicitly,and a second set of configurations or a codepoint may be determinedexplicitly.

An implicit indication may include one or more of the following: (i) aslot size, (ii) a UL/DL configuration of a slot, (iii) a service type,(iv) UCI multiplexing, (v) feedback timing, (vi) feedback type, or (vii)collision of different feedback types. In an example of a slot size, amini-slot may indicate use of a short PUCCH or a regular slot mayindicate use of a long PUCCH. In an example of a UL/DL configuration ofa slot, a WTRU may determine a PUCCH type (e.g., short or long) or along PUCCH duration, for example, based on the number of symbolsassigned for UL transmissions. In an example of a service type, URLLCmay involve a PUCCH format for HARQ that may enable higher reliability.In an example, URLLC transmissions may require PUCCH diversity. In anexample of UCI multiplexing, transmission of HARQ tied to multiple TBs(e.g., due to multiple carriers or slot aggregation) may have a higherpayload PUCCH format. In an example of feedback timing, a feedbacktiming using an offset less than a threshold may use a first PUCCH tablewhile feedback timing using an offset greater than the threshold may usea second PUCCH table. In an example, a short PUCCH may be used, forexample, for a self-contained slot where feedback may be provided in thesame slot as DL data. In an example of a feedback type, HARQ feedbackmay use a first PUCCH configuration while CSI may use a second PUCCHconfiguration. In an example, a transport block (TB)-based HARQ feedbackmay use a first PUCCH configuration (e.g., a short PUCCH) and a codeblock group(CBG)-based HARQ feedback may use a second PUCCHconfiguration. In an example of a collision between different feedbacktypes (e.g., associated with different service types), a PUCCHconfiguration for a service type with higher priority may be used. In anexample, feedback multiplexing may be used on PUCCH configurations forURLLC service, for example, when eMBB HARQ feedback may collide withURLLC HARQ feedback.

Feedback selection based on PUCCH configuration may be provided. In anexample, a WTRU may determine a type of feedback based on the PUCCHconfiguration to be used for the feedback. A WTRU that is assigned withshort PUCCH resources may, for example, determine that a TB-based HARQfeedback may be required for a PDSCH transmission. A WTRU that isassigned with long PUCCH resources may, for example, determine thatCBG-based HARQ feedback may be required. In an example, a WTRU maydetermine a type of CSI feedback, for example, based on a PUCCHconfiguration.

PUCCH transmissions may be multiplexed. In an example, a WTRU may beconfigured to multiplex multiple PUCCH transmissions. Multiplexing maybe achieved, for example, by assigning multiple PUCCH transmissions onthe same resources. A WTRU may be assigned with different frequencyinterlaces, hopping patterns, and/or orthogonal cover code (OCC) foreach of the multiple PUCCH transmissions.

A WTRU may be assigned with resources for multiple PUCCH transmissions.The resources, for example, may be colliding resources. In an example, aWTRU may multiplex multiple UCIs on the same PUCCH resources. In anexample, a WTRU may have a priority ranking associated with UCIs. TheWTRU may drop UCI or feedback with lower priority. In an example, a WTRUmay have a priority ranking associated with the UCIs and may use PUCCHresources for the highest priority UCI and may use another set of PUCCHresources (e.g., a fallback set of PUCCH resources) for another UCItransmission. In an example, a WTRU may use fallback PUCCH resources formultiple UCI transmissions. In an example, each of the multiple UCIs maybe assigned a different fallback resource. Fallback resources may enablemultiplexing (e.g., efficient multiplexing). In an example, a PUCCHconfiguration for a UCI may not use interlacing. In an example, afallback configuration may use an interlacing pattern that may enablemultiplexing. In an example, a PUCCH configuration for a UCI may includea BWP offset (e.g., in the event of a collision with another UCItransmission). In an example, short PUCCH configuration timing (e.g.,symbol(s) location) may depend on whether a UCI transmission mayperceive a collision. In an example, PUCCH hopping configuration maydepend on whether a collision occurs.

Differentiated processing may be provided. Determination of a profileapplicable to a transmission may be provided. A WTRU may process andtransmit UCI, for example, according to a transmission profile (e.g., adetermined transmission profile) that may be associated with the UCI. Atransmission profile may be determined, for example, so that an amountof resources and prioritization may meet a reliability objective for aUCI. Such determination of a transmission profile may allow efficientutilization of resources.

In an example, a transmission profile may be associated with uplink dataor sidelink data. For example, a transmission profile associated withuplink data or sidelink data may be used to allow prioritization betweenuplink data or sidelink data and UCI of different profiles.

Transmission profile applicable to DCI, UCI, or data may be determined.In an example, a transmission profile associated with UCI may beequivalent to or determined from, for example, one or more of thefollowing: (i) a transmission profile for an associated downlink datatransmission (e.g., for a HARQ-ACK or a CSI); (ii) a transmissionprofile for an associated uplink data transmission (e.g., for an SR); or(iii) a bandwidth part on which the UCI is transmitted.

A transmission profile associated with UCI or uplink data may bedetermined, for example, based on one or more of the following: (i) alogical channel or logical channel group from which data may betransmitted based on higher layer configuration (e.g., a transmissionprofile may be configured for each logical channel or logical channelgroup, or the WTRU may determine a transmission profile based on aconfiguration of a logical channel (LCH) to one or more physical layerproperties for a given transmission e.g. a transmission duration orsimilar); (ii) a logical channel or logical channel group of data thatmay have triggered an SR; (iii) a value of a field in DCI that may beassociated with a transmission of UCI or uplink data (e.g., an explicitindication of transmission profile, or implicitly from an existing field(e.g., a HARQ process index) or a field that may be used for logicalchannel prioritization (e.g., for an uplink grant), or a radio networktemporary identifier (RNTI) value that may be used to mask a cyclicredundancy check (CRC); (iv) a property of a PDCCH that may beassociated with a transmission of UCI or uplink data (e.g., a CORESET, amonitoring period, a determination whether the PDCCH is monitored at thebeginning of a slot, a search space or aggregation level that may beused for PDCCH decoding, or a bandwidth part), such as where atransmission profile may be configured (e.g., by higher layers) for aCORESET (e.g., each CORESET) or a PDCCH configuration (e.g., each PDCCHconfiguration); (v) higher layer signaling (e.g., for CSI), and/or afield in DCI that may indicate a set of parameters, for example,configured by higher layers (e.g., a CSI report setting that may beindicated by an aperiodic CSI field); (vi) a property of, or associatedwith, the PDSCH transmission, such as a duration, a bandwidth part, aproperty of the numerology (e.g., a subcarrier spacing, a symbolduration, etc.), a transmission configuration indication (TCI) state(e.g., for HARQ-ACK), a modulation and coding scheme (MCS) tableconfigured or indicated for the control information (e.g., in DCI)associated with the PDSCH transmission; (vii) a property of, orassociated with, the PUCCH resource configured for the transmission ofthe SR (such as a sub-carrier spacing, a duration of PUCCH resource, alogical channel associated to the SR configuration, or a propertythereof, such as a priority, and/or a transmission profile explicitlyconfigured as part of the SR configuration); (viii) a property of, orassociated to, the grant or the PUSCH transmission (e.g., for uplinkdata), for example, a property used for determining a logical channelrestriction for logical channel prioritization (such as a duration ofthe PUSCH transmission, a property of the numerology (e.g., sub-carrierspacing, symbol duration), or a property of the carrier); or (ix) abandwidth part on which an associated PDSCH transmission or PUSCHtransmission is transmitted. With respect to (iv), a transmissionprofile may have precedence based on a priority order that may beconfigured. For example, a transmission profile may have a precedencebased on a configured priority order, if a PDCCH candidate is part ofsearch spaces that are associated with more than one transmissionprofiles. With respect to (i), a transmission profile associated with aUCI may be determined based on an attribute (e.g., a QoS metric)associated with the logical channel or the logical channel group fromwhich data may be transmitted. With respect to (v), a BLER target valuemay be configured for a CSI report setting. The BLER target value mayimplicitly indicate a transmission profile. For example, a lower BLERtarget value may indicate a transmission profile of higher priority. Inan example, the table of CQI reporting may be configured for a CSIreport setting.

A transmission profile for DCI or downlink data may be determined, forexample, based on one or more of the following: (i) a property of aPDCCH from which DCI may be decoded or from which an assignment fordownlink data may be decoded, for example, as disclosed herein for UCIor uplink data (e.g., search space, explicit configuration, etc.); (ii)a modulation and coding scheme (MCS) table indicated for the controlinformation (e.g., in DCI) that is associated with the PDSCHtransmission; such indication may be configured by higher layers or maybe included in a field of the DCI; (iii) the value of a field in DCIthat may be associated with a transmission of downlink data or a RNTIvalue that may be used to mask a CRC; or (iv) a property of, orassociated with, the assignment or the PDSCH transmission (e.g., fordownlink data), such as a duration of the PDSCH transmission, and/or aproperty of the numerology (e.g., a sub-carrier spacing, a symbolduration, etc.)

In an example, a transmission profile may be defined for a physicalchannel (e.g., PDCCH, PUCCH, PDSCH or PUSCH). A transmission profile maybe determined, for example, based on a type of data or controlinformation that may be carried by a physical channel. A transmissionprofile may be set based on the highest priority level among profiles,for example, when a physical channel transmission includes controlinformation and/or data of different profiles (e.g., UCI multiplexed inPUSCH).

Determination of a profile may indicate a timing characteristic. In anexample, a transmission profile may be associated with a timingcharacteristic. Such timing characteristic may correspond to at leastone of the following: (1) scheduling-related delay components, forexample, such component may correspond to one of N1 or N2; (2) WTRUprocessing time, for example, such processing time may correspond to oneof N1 or N2; (3) the starting symbol of a transmission; or (4) theduration of a transmission. N1 and/or N2 may be represent a number ofOFDM symbols as described herein. In an example, a transmission profilemay correspond to a transmission for which one or more such timingcharacteristics up to a value may be provided. The specific value mayrepresent one aspect of a WTRU's configuration. A transmission profilemay be associated with at least one priority level or at least oneparameter determining channel access properties for operation inunlicensed band. For example, the at least one parameter may include amaximum contention window size or a defer duration.

Handling of transmission characteristics based on a profile (e.g., atransmission profile) may be provided. Coding aspects, transmissionpower and/or resource selection or allocation may be determined, forexample, based on a transmission profile as described herein.

In an example, a WTRU may determine one or more aspects that may berelated to channel coding for a physical channel (e.g., PDCCH, PDSCH,PUCCH or PUSCH) from a transmission profile. Coding aspects that may bedetermined may include, one or more of the following: (i) a type of code(e.g., polar, LDPC, turbo, repetition); (ii) a code rate; (iii) a lengthof a cyclic redundancy check (CRC) that may be appended to a set ofinformation bits for error detection; (iv) a mapping between amodulation and coding scheme (MCS) field, and a modulation order and acode rate; or (v) one or more search spaces for one or more aggregationlevels for decoding PDCCH.

In an example, a WTRU may be configured with a CRC of 16 bits for PDCCH,for example, when a higher layer configuration for a PDCCH may indicatea first transmission profile. The WTRU may be configured with a CRC of24 bits, for example, when a configuration may indicate a secondtransmission profile. Using variable CRC size, for example, may allow anetwork to use a more reliable PDCCH transmission, when it may berequired by the characteristics of data being transmitted.

In an example, a coding rate that may be applied to at least one type ofUCI (e.g., HARQ-ACK), may be dependent, for example, on a transmissionprofile. In an example, UCI of multiple transmission profiles may bemultiplexed into the same transmission (e.g., PUCCH). UCI (e.g., eachUCI) may be encoded separately, for example, with a profile-dependentcoding rate. Such encoding may represent a first encoding stage. Codedbits from the first encoding stage associated with each UCI may beconcatenated and subject to a second encoding stage.

Transmission power may be determined based on a transmission profile. Inan example, a WTRU may determine and apply a transmission powerassociated with a transmission. The transmission power may be determinedusing formula and/or parameters that may be dependent on a transmissionprofile. In an example, parameters that may be used in a power controlformula may be configured (e.g., independently configured) for eachtransmission profile. In an example, a power control setting may bebased on an offset value that may be configured by a transmissionprofile. In an example, an interpretation of a TPC field (e.g., in termsof the number of dBs for up or down adjustments) may be dependent on atransmission profile. The use of transmission profile to determinetransmission power may facilitate the use of an appropriate level ofpower to achieve a targeted reliability associated with a transmission(e.g., each transmission).

In an example, the power control parameters applied to a transmission ofa scheduling request (SR) may depend on an SR configuration. The SRconfiguration may be mapped to a logical channel that may have triggeredthe SR.

In an example, the power control parameters applied to a HARQ-ACKtransmission may depend on the duration of the corresponding PDSCHtransmission. For example, if a PDSCH transmission is below a thresholdconfigured by higher layers, the WTRU may apply a first set of powercontrol parameters. If a PDSCH transmission is above a threshold, theWTRU may apply a second set of power control parameters.

In an example, power control parameters applied to the transmission ofHARQ-ACK may depend on an UL bandwidth part (e.g., the active bandwidthpart) on which HARQ-ACK is transmitted, or on the DL bandwidth part onwhich the corresponding PDSCH is transmitted. Each bandwidth part may beconfigured with a set of power control parameters by higher layers.

In an example, power control parameters applied for the transmission ofCSI over PUCCH (or PUSCH) may be dependent on the BLER target valueconfigured for the CSI reporting setting. For example, a WTRU may applya power offset based on the BLER target value. The BLER target value maybe configured by higher layers, for example, for each of the BLER targetvalues. A power offset may be configured, for example, for each CSIreporting setting.

Data or UCI of multiple transmission profiles may be multiplexed in thesame transmission. Power control parameters for a common transmissionmay be determined, for example, based on a profile, for example, aprofile with the highest priority level.

In an example, power control parameters may include a specific powercontrol mode (PCM) or a minimum guaranteed power level. For example, thePCM may include PCM1, PCM2, etc.

A resource selection or allocation may be determined, for example, basedon a transmission profile. In an example, a resource and/or format thatmay be used by a transmission may be a function of a transmissionprofile. For example, in case of PUCCH, a set of resources, and/orformat, indicated by ARI may be dependent on a transmission profile. Anetwork may, for example, configure at least one set of resources for atransmission profile, for example, each transmission profile. A set ofresources that may be subject to lower interference may be associatedwith transmission profiles that may be used for more reliabletransmissions.

In an example, use of a long or short PUCCH format and/or a number ofsymbols may be a function of a transmission profile. In an example, aWTRU may be configured to transmit a PUCCH over multiple symbols (e.g.,two symbols) for a transmission profile (e.g., a first transmissionprofile) that may be suitable for ultra-reliable traffic. A WTRU may beconfigured to transmit a PUCCH over a symbol (e.g., one symbol) foranother transmission profile (e.g., a second transmission profile) thatmay be suitable for other non-ultra-reliable mobile broadband traffic.

In an example, a set of bandwidth parts and numerology (e.g., includingone or more of a sub-carrier spacing, length of a cyclic prefix, ornumber of symbols per slot or mini-slot) may be used for a downlinktransmission or an uplink transmission within a carrier may, forexample, be dependent on a transmission profile.

In an example, a waveform may be dependent on a transmission profile.For example, a waveform may be an orthogonal frequency-divisionmultiplexing (OFDM) waveform or a single-carrier frequency-divisionmultiple access (SC-FDMA) waveform. In an example, use of frequencyhopping may be dependent on a transmission profile.

In an example, with respect to at least one type of UCI (e.g.,HARQ-ACK), the UCI may be transmitted over PUCCH or multiplexed withdata transmitted over a PUSCH. The selection of whether the UCI istransmitted over a PUCCH or multiplexed with data transmitted over aPUSCH may be dependent on transmission profiles associated with the UCIand the data. In an example, a UCI may be multiplexed with data overPUSCH, for example, when UCI and data may have the same transmissionprofile or the same priority level associated with the transmissionprofile. A UCI may be transmitted separately over PUCCH. In an example,at least one type of UCI (e.g., channel state information (CSI)) may bedropped.

In an example, a number or fraction of resource elements that may beused by at least one type of UCI (e.g., when multiplexed with data inPUSCH) may be determined, for example, by one or more factors (e.g.,beta parameters). Such factors may be a function of a transmissionprofile. In an example, for a given type of UCI, a WTRU may beconfigured with a first set of factors that may be applicable to a firsttransmission profile and a second set of factors that may be applicableto a second transmission profile. A transmission profile that may besuitable for ultra-reliable traffic may, for example, permit use of alarger proportion of PUSCH resources.

In an example, a WTRU may determine whether UCI diversity is applied.For example, a SR configuration may include a configuration of PUCCHresources applicable to UCI diversity (or a PUCCH diversity resource).For example, when SR is triggered by a logical channel (LCH) mapped tosuch SR configuration, a WTRU may transmit SR over more than one PUCCHresources (or a PUCCH diversity resource).

Prioritization between transmissions may be provided. In an example, apriority level may be defined or configured for a transmission profile(e.g., each transmission profile). A priority level may be used, forexample, to determine whether one or more transmissions may be droppedor pre-empted, scaled down, assigned fewer resources or processed later,e.g., in case there is contention. An occurrence of contention may bebeneficial (e.g., from a system perspective) for example, by allowinguse of a greater proportion of system resources (e.g., compared to asituation where resources may be reserved).

Prioritization may be provided for power scaling. In an example, a WTRUmay scale down at least one transmission, for example, when a configuredtotal maximum power may be exceeded during a time period (e.g., during asubframe, a slot, or a mini-slot). A priority order for scaling may bedependent on a transmission profile (e.g., in addition to other criteriasuch as UCI or data type). In an example, a transmission profilecriterion may take precedence over, or supersede, other criteria. In anexample, if a first transmission profile has a higher priority levelthan a second transmission profile, a PUSCH that may include data to betransmitted in accordance with the first transmission profile may beallocated power before a PUCCH that may include a HARQ-ACK that is to betransmitted in accordance with the second transmission profile. Theprioritization based on the use of a transmission profile may apply evenwhen HARQ-ACK may otherwise be prioritized over data.

Prioritization may be provided for dropping a transmission or at least aportion of a transmission. In an example, a WTRU may determine that morethan one transmissions may overlap over a subset of resources and thatat least a portion of at least one of the transmissions may be droppedor pre-empted, for example, based on transmission profiles associatedwith the overlapping transmissions. A WTRU may, for example, determinethat a transmission with the highest priority (e.g., based ontransmission profile) may be transmitted over the resource.

An overlap may result, for example, from scheduling instructions thatmay be received at various times and with different latencyrequirements. In an example, a WTRU may receive a downlink assignmentthat may require transmission of HARQ-ACK over PUCCH in certain symbolsof a certain slot. The WTRU may receive a grant (e.g., subsequentlyreceive a grant) for a PUSCH transmission for the same slot. A WTRU maydetermine that the PUSCH transmission takes precedence over the PUCCHtransmission, for example, when the transmission profile associated withthe uplink data that may be transmitted over PUSCH has a higher prioritylevel than the transmission profile associated with the HARQ-ACK thatmay be transmitted over PUCCH. Based on such a determination, a WTRU mayuse overlapping resources for the PUSCH transmission and may drop thePUCCH transmission. In an example, a WTRU may transmit PUCCH over theoverlapped resources. The WTRU may use remaining resources that may beindicated for PUSCH, for example, taking into account a reduced amountof resources in rate matching calculations.

A WTRU may receive a first downlink assignment indicating transmissionof HARQ-ACK over PUCCH in a first resource. The WTRU may receive (e.g.,subsequently receive) a second downlink assignment indicatingtransmission of HARQ-ACK over PUCCH in a second resource. The WTRU maytransmit HARQ-ACK corresponding to PDSCH (or PDCCH) with transmissionprofile of higher priority, for example, if the first resource and thesecond resource overlap or are the same. The WTRU may transmit HARQ-ACKcorresponding to PDSCH (or PDCCH) based on, for example, CORESET, searchspace, and/or RNTI.

In an example, a WTRU may receive a grant for PUSCH over a slot. TheWTRU may receive (e.g., subsequently receive) a downlink assignment (ortrigger a scheduling request) that may require transmission of a PUCCHover one or more resources of the same slot (e.g., over the last timesymbols for a short PUCCH or over one or more time symbols (e.g., mostor all of time symbols) available for uplink for a long PUCCH). A WTRUmay determine that a PUCCH may be transmitted over an overlappedresource, for example, when the PUCCH includes a UCI associated with ahigher transmission profile than data transmitted over a PUSCH. A WTRUmay determine that a PUSCH may be dropped or that PUSCH may betransmitted over a non-overlapped resource, e.g., with puncturingapplied on an overlapped resource. A course of action may depend on atype of pre-empting transmission (e.g., PUSCH may still be transmittedwhen pre-empted by a short PUCCH) and/or whether a proportion of apre-empted resources may be above a threshold.

A WTRU may multiplex HARQ-ACK and CSI into a single PUCCH transmissionor PUSCH transmission and determine that a subset of CSI report(s)(e.g., N_(reported) ^(CSI)) may be selected based on a maximum code ratethat may be configured. The priority order for the CSI report(s) maydepend on a transmission profile (or the configured BLER target value),such that a CSI report associated with a lower BLER target value may beconsidered to have a higher priority than a CSI report associated with ahigher BLER target value. The priority determined from the BLER targetvalue or transmission profile may have precedence over at least one ofother priority criteria used for selection of CSI reports, for example,the type of CSI. For example, this may result in a pre-coding matrixinformation (PM I) of a CSI report associated with a lower BLER targetvalue having higher overall priority than RI (rank information) of a CSIreport associated with a higher BLER target value.

Prioritizing may be provided for DL data processing. In an example, aWTRU may be scheduled to receive DL data with different transmissionprofiles over at least one PDSCH and may report HARQ-ACK (e.g., atspecific times) associated with the DL data. A WTRU may be unable tocomplete decoding of at least one code block in time for transmission ofa corresponding HARQ-ACK. The WTRU may prioritize decoding of DL data ofhigher priority, for example, according to a transmission profileassociated with the DL data.

In an example, a HARQ-ACK may be transmitted before decoding of at leastone code block group is completed for a transport block. Depending onthe transmission profile associated with data, a WTRU may set HARQ-ACKusing one of the following ways. A WTRU may set HARQ-ACK of a not yetdecoded code block group to ACK, for example, when decoding may becompleted and may set it to NACK for at least one other code block groupof the transport block. A WTRU may set HARQ-ACK to an ACK for one ormore code block groups except one that may be set to a NACK. This mayminimize the amount of resources that may be used by a network forretransmissions, for example, in case some, not yet decoded, code blocksmay succeed and not require retransmissions. This example procedure maybe selected, for example, for a transmission profile that may have alower priority.

In an example, a WTRU may set HARQ-ACK of a not yet decoded code blockgroup to NACK. This may minimize latency of a transport block delivery,for example, where retransmitted data may be available sooner, e.g.,when the outcome of the decoding may be unsuccessful. This exampleprocedure may be selected, for example, for a transmission profile thatmay have a higher priority.

Prioritization may be provided for resource sharing. In an example, aWTRU may be configured to multiplex UCI and/or uplink data in accordancewith different transmission profiles into a (e.g., the same) PUSCHtransmission or a PUCCH transmission. A proportion of resource (e.g.,resource elements (REs)) that may be allocated to a UCI or data inaccordance with a transmission profile may depend on relative prioritylevels of the transmission profiles. In an example (e.g., for UCImultiplexing in PUSCH), a first value of a beta parameter for a type ofUCI may be applied, for example, when a priority of a transmissionprofile associated with a UCI is higher than a priority of atransmission profile associated with data. A second value of a betaparameter may be applied, for example, when the transmission profileshave equal priorities. A third value may be applied, for example, when apriority of a transmission profile associate with a UCI is lower than apriority associated with a transmission profile of data.

Payload/MCS selection may be based on prioritization. In an example, aWTRU may be configured to use a first modulation and coding scheme,transport block size, and/or payload for a transmission, for example,when the transmission may not conflict with a transmission of a higherpriority according to a transmission profile. A WTRU may be configuredto use a second modulation and coding scheme, transport block size orpayload for a transmission, for example, when the transmission conflictswith a transmission of a higher priority according to a transmissionprofile. A conflict may correspond to a situation, for example, whenresources of multiple transmissions may overlap or when a configuredmaximum total transmission power may be exceeded.

State-based differentiated processing may be provided. In an example, aWTRU may apply a set of parameters corresponding to a transmissionprofile (e.g., based on the transmission profile state). Thetransmission profile state may be changed by an indication from thenetwork. For example, the transmission profile state may be changed viaa MAC control element (MAC CE) or via downlink control information(DCI). The transmission profile state may be changed when an eventoccurs, such as the expiry of a timer (e.g., a timing advance (TA)timer). The set of parameters corresponding to a transmission profilemay include a set of PUCCH resources for HARQ ACK/NACK, a set ofparameters used for determining the fraction of resource elements usedfor UCI in PUSCH, etc.

In an example, a transmission profile and associated parameters may beconfigured for a bandwidth part. A WTRU configured with multiplebandwidth parts may apply the transmission profile and associatedparameters corresponding to an active bandwidth part. The WTRU mayreceive a DCI or a MAC CE indicating a change of active bandwidth part.The WTRU may (e.g., upon reception of this indication) apply thetransmission profile and associated parameters associated with thereceived (or indicated) active bandwidth part.

In an example, a WTRU may receive a DCI indicating a change of activebandwidth part (for example, where the new active bandwidth part and theexisting active bandwidth part may share the same configuration exceptfor at least the transmission profile and associated parameters). Forexample, the WTRU may be configured with two bandwidth parts with samefrequency allocation. When the WTRU receives an indication of activebandwidth part change (e.g., that meets this condition), the WTRU mayreceive a PDSCH in the same slot as the slot in which the DCI isreceived based on the parameters indicated in the DCI (e.g., as if thereis no change of active bandwidth part). In an example, if a WTRUreceives an indication of active bandwidth part where the new activebandwidth part does not have the same frequency allocation as theexisting active bandwidth part, the WTRU may apply a gap in thereception of PDSCH (e.g., to allow for retuning and/or to perform otheractions (e.g., CSI measurements on the new active bandwidth part)).

Systems, methods, and instrumentalities may be provided for handling oftransmission characteristics with an overlap between a plurality oftransmissions. A WTRU may determine that an overlap exists in timebetween a plurality of transmissions, e.g., a first transmission and asecond transmission. The WTRU may perform at least one of the following:(1) perform a subset (e.g., one) one of the transmissions; (2) cancel,drop or interrupt (e.g., if already ongoing) one of the transmissions;(3) suspend and/or delay one of the transmissions; (4) perform bothtransmissions, and/or apply a power scaling function to at least onetransmission e.g., if there is no overlap in frequency between thetransmissions; or (5) modify at least one property of a firsttransmission e.g., to convey at least part of the information that mayhave otherwise been conveyed using a second transmission. For example, aWTRU may modify a property of a demodulation reference signal (DM-RS)for a first PUSCH transmission to indicate a scheduling request (SR).Modification, for example, may include assigning zero power, changing toa second preconfigured resource, changing phase, etc. The WTRU mayperform such action in combination with assigning zero power to a secondtransmission e.g., SR on PUCCH, that may have otherwise overlapped intime.

In other examples of transmissions described herein, a firsttransmission may include an SR and a second transmission may include aPUSCH (or a PUCCH). An SR associated with high-priority traffic may bemultiplexed with PUSCH or PUCCH. A WTRU may indicate and/or transmituplink control information such as SR associated with a firsttransmission profile by modifying at least one property of atransmission associated with a second transmission profile, such as aPUSCH transmission or a PUCCH transmission. In an example, the firsttransmission profile may have higher priority than the secondtransmission profile. In an example, the duration of the PUSCHtransmission or the PUCCH transmission may be longer (e.g.,significantly longer) than the periodicity of the scheduling request forthe first transmission profile. The length of the PUSCH transmission orthe PUCCH transmission may be of nature that waiting for the end of thePUSCH transmission or the PUCCH transmission before transmitting the SRmay exceed a latency value (e.g., an acceptable latency value).

The at least one property of the transmission that may be modified mayinclude a property of a reference signal embedded in the transmission,such as a demodulation reference signal (DM-RS). For example, suchproperty may include a relative phase between two time symbols carryingDM-RS. The relative phase may be a first value, for example, if no SR istransmitted. The relative phase may be a second value if a schedulingrequest is transmitted.

The at least one property of the transmission that may be modified mayinclude a transmission power parameter of at least one time symbol (or aresource element). For example, transmission power of at least onesymbol may be reduced as compared to transmission power of the remainingsymbols, when SR is transmitted. In an example, the transmission powerof the at least one symbol may be reduced to zero and/or the WTRU maynot transmit on the at least one symbol. This may allow the network toreliably detect the transmission of SR, and allow successful decoding ofthe PUSCH.

The at least one time symbol (or resource element) over which atransmission may be modified may be restricted to a subset of the timesymbols of the transmission. For example, if the indication is carriedby modification of a property of a reference signal, the time symbolsmay be restricted to time symbols carrying such reference signal. Thetime symbols affected by the modification may include the time symbols(e.g., all time symbols) carrying the reference signal followingtriggering of the SR. In an example, if the indication is carried bymodification of transmission power of at least one time symbol, thesubset may be determined based on a configured periodicity of thescheduling request. The at least one affected time symbol may include asingle symbol or the time symbols (e.g., all time symbols) immediatelyfollowing triggering of SR that may coincide with configured occasionsof the scheduling request. In an example, one or more time symbolsincluding reference signals may be excluded from the subset.

In an example, a subset of resource elements (or time symbols) of aPUSCH transmission or a PUCCH transmission may be configured to indicateif SR has been triggered since the beginning of the transmission. A WTRUmay be configured with at least one such subset of resource elementsoccurring regularly (e.g., periodically) in the time domain. Suchconfiguration may depend on a configured periodicity of the SR, or maycoincide with configured occasions for the transmission of SR. Over agiven subset, a WTRU may transmit a first pre-defined sequence ofmodulated symbols, for example, if an SR has not been triggered until anoffset before the time symbol(s) of the subset. The WTRU may transmit asecond pre-defined sequence of modulated symbols, for example, if an SRhas been triggered. The pre-defined sequence may over-write (e.g., usingpuncturing) modulated symbols of the PUSCH or the PUCCH that may havebeen mapped (e.g., previously mapped) to the subsets of resourceelements or the subsets of resource elements may have been excluded atthe outset from the set of resource elements to which modulated symbolsof the PUSCH or PUCCH transmission are mapped.

Systems, methods, and instrumentalities may be provided for handling oftransmission characteristics based on timing may be provided. One ormore aspects may be determined as a function of available WTRUprocessing, e.g., WTRU processing time.

A WTRU may determine that it may apply at least one prioritization ormultiplexing solution. The prioritization or multiplexing solution maybe a function of one or more timing aspects including, for example, atleast one of the following: (1) Timing aspect of when data may beavailable for transmission, or when data available for transmission maytrigger transmission of a BSR and/or transmission of an SR; (2) timingaspect of when a scheduling request (SR) may be triggered; (3) timingaspect of when downlink control information indicating an uplinktransmission (e.g., a PUSCH transmission or a PUSCH transmission) may bereceived; (4) timing aspect of reception of higher layer signaling, forexample, at least in case of a configured grant or of another periodicor semi-persistent transmission (e.g., CSI, SRS); (5) timing aspect ofwhen a PUSCH transmission may be scheduled to start (and/or end)according to a configured or dynamic grant; (6) timing aspect of when aPUCCH transmission may start (and/or end), for example, according to asemi-static configuration or an indication from downlink controlinformation; (7) the duration of a PUSCH or PUCCH transmission; or (8)timing aspect of when a transmission may be determined to exist in thefuture for any other reasons, for example, reception of a pagingrequest, initiation of a procedure such as RRC ConnectionRe-establishment, etc. In case of (1), for example, a WTRU may performsuch determination when new data may become available for transmissionfor a logical channel (LCH) of a specific priority and/or type, or whendata available for transmission may trigger the transmission of a bufferstatus report (BSR) and/or of a SR. The WTRU may perform suchdetermination for data associated with a mapping restriction (e.g., (LCHto transmission mapping restriction), a profile and/or a LCH/logicalchannel group (LCG) priority.

A WTRU may perform such determination of applying at least one ofprioritization or multiplexing solution for data and/or for atransmission associated with a specific (LCH to transmission) mappingrestriction, to a specific profile and/or to a specific LCH/LCGpriority. For example, a WTRU may determine the prioritization ormultiplexing solution that may be applied for at least two or moretransmissions (e.g., partially overlapping transmissions). Thedetermination may be made based on the difference between the start timeof a first transmission and the time when a second transmission isdetermined to exist, as described herein.

A WTRU may perform a first action 1 (Action 1) or a second action 2(Action 2), for example, if the WTRU determines that a first event A(Event A) occurs at least x symbol(s) of time before the start of eventB (Event B). The event B may be a known event.

One or more timing cases may be provided to indicate that an SR triggermay be a function of suitability of grant. Event A may correspond to aWTRU autonomous trigger associated with the reception of downlinkcontrol signaling and/or to an event that may correspond to a higherpriority than that of Event B (e.g., based on an applicable transmissionprofile). The autonomous trigger may be one of the timing aspects asdescribed herein, for example, triggering an SR, when new data maybecome available for transmission. Event B may correspond to a scheduledevent (e.g. an uplink transmission).

In Action 1, a WTRU may determine that a sufficient time is available toact on the scheduled information and/or prioritize one of the two eventsbefore the event of lesser priority is started. In Action 2, a WTRU maydetermine that there is insufficient time to adjust its transmissionsand/or prioritize one of the two events before the event of lesserpriority is started such that it may instead determine to modify theproperties of the corresponding ongoing transmission. The WTRU may beconfigured with a value of x e.g., by RRC, where x may be a time valuein symbols, in a framing unit (e.g., mini-slot, slot, subframe) or inabsolute time, e.g., in milliseconds.

In an example, event A may correspond to a SR trigger for dataassociated with a transmission profile, for example, a transmissionprofile corresponding to transmission of URLLC data. Event B maycorrespond to the start of an uplink transmission on PUSCH for dataassociated with a transmission profile, for example, a transmissionprofile corresponding to transmission of eMBB data.

Action 1 may correspond to cancellation of an uplink transmission, e.g.,the PUSCH transmission corresponding to eMBB data, and the WTRUperforming an SR transmission using a resource/method corresponding toURLLC type of data. Action 2 may correspond tocancellation/dropping/zero power setting of one or more specificsymbol(s) and/or a DM-RS modification of PUSCH transmission for eMBB,e.g., to indicate SR for URLLC, as described herein.

In an example, one of the transmission may correspond to a firsttransmission profile or similar e.g., a URLLC service and another maycorrespond to a second transmission profile, e.g., an eMBB service. Insuch an example, if a WTRU determines that there is sufficientprocessing time (e.g., time between two events is less than x), and ifthe WTRU makes this determination before the start of any one of thetransmissions that at least partially overlap, the WTRU may perform atleast one of the following for different combinations of signals: (1)the WTRU may prioritize SR(for URLLC), drop PUSCH(for eMBB); (2) theWTRU may prepend and/or puncture PUSCH(for eMBB) with SR(for URLLC),e.g., using a similar concatenation principle as used for UCI on PUSCHfor LTE; (3) the WTRU may embed transmission, e.g., drop a part ofPUSCH(for eMBB) and replace it with sPUSCH (including BSR(for URLLC));(4) the WTRU may signal SR using a modification to the DM-RS sequence ofthe PUSCH(for eMBB); (5) the WTRU may adjust UL PC, e.g., apply powerscaling, e.g., if the WTRU is power limited.

In an example, if the WTRU determines that there is not sufficientprocessing time (e.g., time between two events is less than x), or ifthe WTRU does not make this determination before the start of any one ofthe transmissions that at least partially overlap, the WTRU may performat least one of the following for different combinations of signals: (1)the WTUR may preempt/interrupt or puncture an ongoing PUSCH (for eMBB),and the WTRU may transmit SR(for URLLC) using an associated resource,e.g., on short PUCCH instead, transmit BSR (for URLLC), e.g., shortPUSCH (for URLLC) instead, and/or transmit a URLLC TB, e.g., shortPUSCH(for URLLC) instead; (2) the WTRU may signal SR using change ofDM-RS sequence for the ongoing PUSCH(for eMBB); (3) the WTU may adjustUL PC accordingly (e.g., for DM-RS boosting).

In an example, a WTRU may initiate an additional transmission on thesame carrier, for example, if the WTRU is configured with simultaneousPUSCH+PUSCH or PUSCH+PUCCH. The WTRU may send the additionaltransmission in the same bandwidth part or in a different bandwidthparts, for example, if configured and/or active. The WTRU may performsuch transmission using disjoint resources and/or joint resources.Disjoint resources may include separate PUSCH and/or PUCCH transmissionsthat may be started with other ongoing transmission(s). Joint resourcesmay be used, for example, when URLLC is configured, and/or any grant forother type of traffic (e.g., of lesser priority) may include resourcesfor additional transmissions of SR, BSR.

A WTRU may allocate power using one or more power control functions. AWTRU may consider transmissions that may be transmitted with at least apartial overlap in time, but for which the WTRU may not have made adetermination whether or not such transmission will be transmitted. TheWTRU may include following factors in making the determination ofwhether or not to transmit such a transmission: the respective priorityin the power allocation function, the method, and/or the resources thatmay be used, e.g., if performed for maximum power reduction (MPR)setting.

The systems and/or methods described herein may be implemented in acomputer program, software, and/or firmware incorporated in acomputer-readable medium for execution by a computer and/or processor.Examples of computer-readable media may comprise electronic signals(transmitted over wired and/or wireless connections) and/orcomputer-readable storage media. Examples of computer-readable storagemedia may comprise a read only memory (ROM), a random-access memory(RAM), a register, cache memory, semiconductor memory devices, magneticmedia such as, but not limited to, internal hard disks and removabledisks, magneto-optical media, and/or optical media such as CD-ROM disks,and/or digital versatile disks (DVDs). A processor in association withsoftware may be used to implement a radio frequency transceiver for usein a WTRU, terminal, base station, RNC, and/or any host computer.

1-16. (canceled)
 17. A wireless transmit/receive unit (WTRU) comprising:a receiver configured to receive at least one physical downlink controlchannel (PDCCH) transmission comprising downlink control information(DCI); a processor configured to at least: determine one or moretransmission characteristics associated with an uplink controlinformation (UCI), wherein the one or more transmission characteristicsare determined based at least one attribute associated with the receivedat least one PDCCH transmission and an attribute of data associated withthe UCI, wherein the PDCCH transmission is mapped to one or moreresources of a control resource set (CORESET), wherein the one or moretransmission characteristics comprise one or more of: at least onecoding parameter, at least one transmission power parameter, at leastone resource allocation parameter, or a priority level; and atransmitter configured to transmit the UCI over a physical uplinkcontrol channel (PUCCH), wherein the UCI is transmitted using thedetermined transmission characteristics.
 18. The WTRU of claim 17,wherein the transmitter is configured to transmit the UCI based on oneor more of: the CORESET, a search space, or a radio network temporaryidentifier (RNTI).
 19. The WTRU of claim 17, wherein the one or moretransmission characteristics are determined based on one or more of: atleast one DCI field in the received DCI, or an identity of a bandwidthpart (BWP) used for transmitting at least one of the DCI or the UCI. 20.The WTRU of claim 17, wherein the DCI comprises a first DCI and a secondDCI, wherein the first DCI is received using a first control resourceset (CORESET) and the second DCI is received using a second CORESET. 21.The WTRU of claim 20, wherein each of the first CORESET or the secondCORESET comprises one or more of a component carrier, at least one BWP,a subset of resource blocks within each bandwidth part, a set of timesymbols within a slot or mini-slot, a sub-carrier spacing, a subset ofslots within a subframe, or at least one reference signal.
 22. The WTRUof claim 20, wherein the UCI comprises feedback information bitsassociated with one or more of the first DCI or the second DCI.
 23. TheWTRU of claim 20, wherein the UCI comprises a first UCI and a secondUCI, wherein the first UCI or the second UCI comprises feedbackinformation bits for a data transmission allocated by the first DCI orthe second DCI.
 24. The WTRU of claim 17, wherein the UCI comprises afirst UCI and a second UCI, wherein the second UCI corresponds to aredundant transmission of the first UCI.
 25. The WTRU of claim 24,wherein the first UCI or the second UCI comprises one or more of ahybrid automatic repeat request (HARQ), a scheduling request (SR), or achannel quality indicator (CQI).
 26. The WTRU of claim 17, wherein theattribute of data is at least one of: an identity of a logical channelor an identity of a logical channel group of the data associated withthe UCI, wherein the attribute is a quality of service (QoS) metric. 27.A uplink control information (UCI) transmission method comprising:receiving at least one physical downlink control channel (PDCCH)transmission comprising downlink control information (DCI); determiningone or more transmission characteristics associated with an uplinkcontrol information (UCI), wherein the one or more transmissioncharacteristics are determined based on at least one attributeassociated with the received at least one PDCCH transmission and anattribute of data associated with the UCI, wherein the PDCCHtransmission is mapped to one or more resources of a control resourceset (CORESET), wherein the one or more transmission characteristicscomprise: one or more of at least one coding parameter, at least onetransmission power parameter, at least one resource allocationparameter, or a priority level; and transmitting the UCI over a physicaluplink control channel (PUCCH), wherein the UCI is transmitted using thedetermined transmission characteristics.
 28. The method of claim 27further comprising transmitting the UCI based on one or more of: theCORESET, a search space, or a radio network temporary identifier (RNTI).29. The method of claim 27, wherein the one or more transmissioncharacteristics are determined based on one or more of: at least one DCIfield in the received DCI, or an identity of a bandwidth part (BWP) usedfor transmitting at least one of the DCI or the UCI.
 30. The method ofclaim 27, wherein the DCI comprises a first DCI and a second DCI,wherein the first DCI is received using a first control resource set(CORESET) and the second DCI is received using a second CORESET.
 31. Themethod of claim 30, wherein each of the first CORESET or the secondCORESET comprises one or more of a component carrier, at least one BWP,a subset of resource blocks within each bandwidth part, a set of timesymbols within a slot or mini-slot, a sub-carrier spacing, a subset ofslots within a subframe, or at least one reference signal.
 32. Themethod of claim 30, wherein the UCI comprises feedback information bitsassociated with one or more of the first DCI or the second DCI.
 33. Themethod of claim 30, wherein the UCI comprises a first UCI and a secondUCI, wherein the first UCI or the second UCI comprises feedbackinformation bits for a data transmission allocated by the first DCI orthe second DCI.
 34. The method of claim 27, wherein the UCI comprises afirst UCI and a second UCI, wherein the second UCI corresponds to aredundant transmission of the first UCI.
 35. The method of claim 34,wherein the first UCI or the second UCI comprises one or more of ahybrid automatic repeat request (HARQ), a scheduling request (SR), or achannel quality indicator (CQI).
 36. The method of claim 27, wherein theattribute of data is an identity of a logical channel a logical channelgroup of the data associated with the UCI, wherein the attribute is aquality of service (QoS) metric.